Intermediary transaction http://www.aliyun.com/zixun/aggregation/6858.html ">seo diagnose Taobao guest cloud host technology Hall
in general, many friends do not care about IIS logs, or because the purchase of a virtual host is not provided, some provided, but also must contact the server administrator to get. 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 pay attention to 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.
Below is a description of the fields and descriptions that are recorded in the IIS?
Date: When the request was issued.
time: When the request is issued. 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 an event running on the client.
S-computername: 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 resources that record 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 a 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.
the 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 issued in the last few days of the Chxwei blog.
sc-bytes: Number of bytes sent by the server.
cs-bytes: Number of bytes accepted by the server.
Time-taken: The time it takes to record the operation, 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 site may appear differently in the log file because HTTP.sys uses the Punycode encoding format to record the host name.
CS (user): 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.
: Time issue with IIS logs
GMT Time is the United Kingdom GMT, that is, the world standard Time, is Meridian on the place, is 0 time zone, and China's standard Time (East eight) Difference 8 hours, that is, 8 hours late.
Annex II: HTTP status code:
Summary:
1**: Request received, continue processing
2**: Indicates that the operation was successfully received, analyzed, accepted
3**: Indicates that this request must be processed further
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 requests
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 the processing is incomplete
203--return information is uncertain or incomplete
204--request received, but the return message is empty
205--Server completes the request, the user agent must reset the files that are currently browsed
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
305--The requested resource 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--affirms that the requested resource is temporarily deleted
400--error requests, such as syntax errors
401--Request Authorization failed
402--retains a valid Chargeto header response
403--request does not allow
404--did not find a file, query, or URL
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
408--Client does not complete the request within the time specified by the user
409--The current resource state, the request cannot be completed
410--Server no longer has this resource and no further reference address
411--server rejects user-defined Content-length property requests
412--One or more request header fields are incorrect in the current request
The resource requested by
413--is larger than the size allowed by the server
414--The requested resource URL is longer than the length allowed by the server
415--Request resource does not support request item format
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 server does not meet the request
500--server generates internal error
501--Server does not support the requested function
502--servers are temporarily unavailable, sometimes to prevent system overload
503--server overload or suspend repair
504--Gateway overload, the server uses another gateway or service to respond to users, waiting time set value longer
505--Server does not support or reject the HTTP version specified in the Support request header
Source: http://www.chxwei.com/article.asp?id=350
