Search results
Results from the WOW.Com Content Network
414 URI Too Long The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request. Called "Request-URI Too Long" previously. [16]: §10.4.15 415 Unsupported Media Type
404.10 – Request header too long. 404.11 – Request contains double escape sequence. 404.12 – Request contains high-bit characters. 404.13 – Content length too large. 404.14 – Request URL too long. 404.15 – Query string too long. 404.16 – DAV request sent to the static file handler.
Data connection already open; transfer starting. 150: File status okay; about to open data connection. 200 Series: The requested action has been successfully completed. 202: Command not implemented, superfluous at this site. 211: System status, or system help reply. 212: Directory status. 213: File status. 214: Help message.
413 Request Entity Too Large Request body too large. [1]: §21.4.11 414 Request-URI Too Long The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. [1]: §21.4.12 415 Unsupported Media Type Request body in a format not supported. [1]: §21.4.13 416 Unsupported URI Scheme
The client submits an HTTP request message to the server. The server, which provides resources such as HTML files and other content or performs other functions on behalf of the client, returns a response message to the client. The response contains completion status information about the request and may also contain requested content in its ...
The date and time that the message was sent (in "HTTP-date" format as defined by RFC 9110) Date: Tue, 15 Nov 1994 08:12:31 GMT: Permanent RFC 9110: Delta-Base: Specifies the delta-encoding entity tag of the response. [11] Delta-Base: "abc" Permanent RFC 3229: ETag: An identifier for a specific version of a resource, often a message digest
Get AOL Mail for FREE! Manage your email like never before with travel, photo & document views. Personalize your inbox with themes & tabs. You've Got Mail!
Messages communicated via OCSP are encoded in ASN.1 and are usually communicated over HTTP. The "request/response" nature of these messages leads to OCSP servers being termed OCSP responders. Some web browsers (e.g., Firefox [4]) use OCSP to validate HTTPS certificates, while others have disabled it.