Description of the IIS www logging fields and HTTP status Codes _win server

Like a new network of parts of the server FTP directory has this file, but is prompted not to view and do not have permission to download, but also have to call them to be able to.

As the site owner, we should focus on the IIS log, from which we can not only see the site's Access records and search engine crawl records, you can also see which sites hotlinking the site of which resources, partial dead links and other error messages. In fact for us, spiders crawl records and related error information is our most want to focus on. Which spiders what time crawls what page, return what result, whether normal, can see from the log clearly.

The following is a list of the fields and descriptions that are recorded in the IIS Universal format log (typically the selected universal format journal).

Date: The day when the request was issued.
Time: When the request is made. Note: This time by default is GMT, which is 8 hours later than our Beijing time, as explained below.
C-IP: Client IP address.
Cs-username: User name, the name of the authenticated user who accessed the server, and the anonymous user is represented by a connector.
S-sitename: Service name, record the number of the name and instance of the Internet service that logged the event running on the client.
S-computername: The name of the server.
S-IP: The IP address of the server.
S-port: The server port number configured for the service.
Cs-method: HTTP method used in the request, Get/post.
Cs-uri-stem:uri A resource that records the Uniform Resource Identifier (URI) that is the target of the operation, that is, the paging file that is accessed.
Cs-uri-query:uri query, record the client tries to execute the query, only the dynamic page requires a URI query, if there is a record, not the connector-represented. That is, an accompanying parameter to access the URL.
Sc-status: Protocol status, record HTTP status code, 200 for success, 403 for no permissions, 404 for the page not found, specify below.
Sc-substatus: Protocol sub State, logging HTTP child status code.
Sc-win32-status:win32 status, log the Windows status code, and refer to the description of the log "Sc-win32-status--win32 status details in IIS", which was sent in the Chxwei blog.
Sc-bytes: The number of bytes sent by the server.
Cs-bytes: The number of bytes accepted by the server.
Time-taken: Records the time that the operation took, in milliseconds.
Cs-version: Log the protocol version used by the client, HTTP or FTP.
Cs-host: Record host header name, no words in connector-represented. Note: the hostname configured for the Web site may appear in a different way in the log file because HTTP.sys uses the Punycode encoding format to record the host name. Special Note: This site all reproduced articles do not represent the views of the site, the site provides photographic photos, illustrations, design works, if necessary, please contact the original author
CS (user-agent): User agent, client browser, operating system and so on.
CS (Cookie): Record the content of the cookies sent or received, if not, with a connector.
CS (Referer): Refers to the site, that is, the source of access.

Annex I: Time issue with IIS logs

GMT time is the British GMT, that is, the world standard Time, is the place on the meridian, is 0 time zone, and China's standard Time (East eight) Difference 8 hours, that is, 8 hours late.

Annex II: HTTP status code:

Summarized:

1**: Request received, continue processing
2**: Indicates successful receipt, analysis, acceptance of operation
3**: Indicates that the request must be further processed to complete
4**: Indicates that the request contains an error syntax or cannot be completed
5**: Indicates that the server failed to perform a fully valid request

Detailed Code Description:

100--customer must continue to issue a request
101--client requires the server to convert the HTTP protocol version on request

200--Trading Success
201--prompts to know the URL of the new file
202--accept and process, but processing incomplete

203--return information is uncertain or incomplete
204--request received, but return information is empty
The 205--server completes the request and the user agent must reset the files that are currently browsed
The 206--server has completed some of the user's Get requests

300--requested resources can be obtained in multiple places
301--Delete request data
302--found request data at other addresses
303--advises customers to access other URLs or access methods
The 304--client has executed a GET, but the file has not changed
The resource requested by 305--must be obtained from the address specified by the server
306--the code used in the previous version of HTTP, which is no longer used in the current version
307--declare the requested resource to be temporarily deleted

400--error requests, such as syntax errors
401--Request Authorization failed
402--retains a valid Chargeto header response
403--Request not allowed
404--found no files, queries, or URLs
405--the method defined by the user in the Request-line field does not allow
406--requests that the resource is inaccessible based on the accept dragged by the user.
407--is similar to 401, the user must first be authorized on the proxy server
The 408--client did not complete the request within the time specified by the user
409--the current resource state, the request cannot be completed
This resource is no longer available on the 410--server and there is no further reference address
411--server rejects user-defined Content-length property request
412--one or more request header fields errors in the current request
413--requested resource is greater than the size allowed by the server
414--The requested resource URL is longer than the length allowed by the server
Request item format not supported by 415--request Resource
The 416--request contains a range request header field, there is no range indicating value within the current request resource range, and the request does not contain a If-range request header field
417--server does not meet the expected value specified by the request Expect header field, if it is a proxy server, it may be that the next level of server does not meet the request

500--Server generates internal error
The requested function is not supported by the 501--server
502--servers are temporarily unavailable, sometimes to prevent system overload
503--server overload or suspend repair
504--Gateway overload, the server to use another gateway or service to respond to users, waiting time set a longer special attention: This site all reproduced article comments do not represent the views of the site, the site provides photographic photos, illustrations, design works, if necessary, please contact the original author.
505--server does not support or reject the HTTP version specified in the Support request header