Http Status Code Cache Information Error Information Log
Contents |
sections of messages Error, Forward and redirection responses may be used to contain human-readable diagnostic information. Success 2xx These codes indicate success. The body section if present is the object returned by the request. It http status code 400 is a MIME format object. It is in MIME format, and may only be in
Http Response Example
text/plain, text/html or one fo the formats specified as acceptable in the request. OK 200 The request was fulfilled. CREATED 201 Following a
Status Code 404
POST command, this indicates success, but the textual part of the response line indicates the URI by which the newly created document should be known. Accepted 202 The request has been accepted for processing, but the processing
Http Status Codes Cheat Sheet
has not been completed. The request may or may not eventually be acted upon, as it may be disallowed when processing actually takes place. there is no facility for status returns from asynchronous operations such as this. Partial Information 203 When received in the response to a GET command, this indicates that the returned metainformation is not a definitive set of the object from a server with a copy of the object, but is http 418 from a private overlaid web. This may include annotation information about the object, for example. No Response 204 Server has received the request but there is no information to send back, and the client should stay in the same document view. This is mainly to allow input for scripts without changing the document at the same time. Error 4xx, 5xx The 4xx codes are intended for cases in which the client seems to have erred, and the 5xx codes for the cases in which the server is aware that the server has erred. It is impossible to distinguish these cases in general, so the difference is only informational. The body section may contain a document describing the error in human readable form. The document is in MIME format, and may only be in text/plain, text/html or one for the formats specified as acceptable in the request. Bad request 400 The request had bad syntax or was inherently impossible to be satisfied. Unauthorized 401 The parameter to this message gives a specification of authorization schemes which are acceptable. The client should retry the request with a suitable Authorization header. PaymentRequired 402 The parameter to this message gives a specification of charging schemes acceptable. The client may retry the request with a suitable ChargeTo header. Forbidden 403 The request is for something forbidden. Author
consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any http status code 0 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client http code 302 except under experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, http 422 even if the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection between the proxy and its https://www.w3.org/Protocols/HTTP/HTRESP.html client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) Wikipedia Request received, continuing process. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 http://www.restapitutorial.com/httpstatuscodes.html did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions. 100 Continue The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code. Wikipedia This means that the server has received the request headers, and that the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue status code is recei
resources Windows Server 2012 resources Programs MSDN subscriptions Overview Benefits Administrators Students Microsoft Imagine Microsoft Student Partners ISV Startups TechRewards Events Community Magazine Forums Blogs Channel 9 Documentation APIs and reference Dev centers Samples Retired content We’re sorry. The content https://msdn.microsoft.com/en-us/library/aa503433.aspx you requested has been removed. You’ll be auto redirected in 1 second. Administration COM Documentation Administration Reference Log Fields Log Fields Web Proxy Log Fields Web Proxy Log Fields Web Proxy Log Fields Firewall Log Fields Web Proxy Log Fields SMTP Message Screener Log Fields TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and status code is not being maintained. Web Proxy Log Fields Internet Security and Acceleration Server 2004/2006 SDK The following table lists the log fields that can be included in ISA Server Web proxy log entries by setting the corresponding bit in the LogFieldSelection property of the FPCLog object for Web proxy logging. Bit number Field name (log viewer) Field name (MSDE databases) Field name (W3C files) Description 0 Client IP ClientIP c-ip The Internet Protocol (IP) address of the http status code requesting client. 1 Client Username ClientUserName cs-username The account of the user making the request. A question mark (?) next to the user name indicates that the user name was sent but the user was not authenticated by ISA Server. If ISA Server access control is not being used, ISA Server uses Anonymous. 2 Client Agent ClientAgent c-agent The name and version of the client application sent by the client in the Hypertext Transfer Protocol (HTTP) User-Agent header. When ISA Server is actively caching, this field is set to ISA Server. 3 Authenticated Client ClientAuthenticate sc-authenticated A value that indicates whether the client has been authenticated with the ISA Server computer. Possible values are Y and N. 4 Log Date logTime date The date on which the logged event occurred. In the MSDE format, both the date and the local time are included in the single logTime field, and the bits for both the date and time fields must be set. 5 Log Time logTime time The local time when the logged event occurred. In the W3C extended file format and in ODBC-compliant SQL Server databases, this time is in Coordinated Universal Time (UTC). In the MSDE format, both the date and the local time are included in the si