|
The following is a list of HTTP response status codes and standard associated phrases, intended to give a short textual description of the status. These status codes are specified by RFC 2616, along with additional codes, some from the Distributed Authoring (WebDAV) extension. Others are unstandardised but commonly used. Hypertext Transfer Protocol (HTTP) is a method used to transfer or convey information on the World Wide Web. ...
WebDAV was an IETF working group. ...
The first digit of the status code specifies one of five classes of response.
1xx Informational
Request received, continuing process. - 100 Continue
- 101 Switching Protocols
- 102 Processing (WebDAV)
2xx Success The action was successfully received, understood, and accepted. - 200 OK
- 201 Created
- 202 Accepted
- 203 Non-Authoritative Information (since HTTP/1.1)
- 204 No Content
- 205 Reset Content
- 206 Partial Content
- 207 Multi-Status (WebDAV)
- The message body that follows is an XML message and can contain a number of separate response codes, depending on how many sub-requests were made.
The Extensible Markup Language (XML) is a W3C-recommended general-purpose markup language that supports a wide variety of applications. ...
3xx Redirection The client must take additional action to complete the request. - 300 Multiple Choices
- 301 Moved Permanently
- This and all future requests should be directed to another URI.
- 302 Found
- This is the most popular redirect code, but also an example of industrial practice contradicting the standard. HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented it as a 303 See Other. Therefore, HTTP/1.1 added status codes 303 and 307 to disambiguate between the two behaviors. However, majority of Web applications and frameworks still use the 302 status code as if it were the 303.
- 303 See Other (since HTTP/1.1)
- The response to the request can be found under another URI using a GET method.
- 304 Not Modified
- 305 Use Proxy (since HTTP/1.1)
- Many HTTP clients (such as Mozilla and Internet Explorer) don't correctly handle responses with this status code.
- 306 Switch Proxy
- No longer used.
- 307 Temporary Redirect (since HTTP/1.1)
- In this occasion, the request should be repeated with another URI, but future requests can still be directed to the original URI. In contrast to 303, the original POST request must be repeated with another POST request.
Mozilla was the official, public, original name of Mozilla Application Suite by the Mozilla Foundation, nowadays called SeaMonkey suite. ...
It has been suggested that Internet Explorer 7 be merged into this article or section. ...
4xx Client Error The request contains bad syntax or cannot be fulfilled. - 400 Bad Request
- 401 Unauthorized
- Similar to 403 Forbidden, but specifically for use when authentication is possible but has failed or not yet been provided. See basic authentication scheme and digest access authentication.
- 402 Payment Required
- The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code has never been used.
- 403 Forbidden
- 404 Not Found
- 405 Method Not Allowed
- 406 Not Acceptable
- 407 Proxy Authentication Required
- 408 Request Timeout
- 409 Conflict
- 410 Gone
- Indicates that the resource requested is no longer available. This should be used when a resource has been intentionally removed; however, in practice, files are often simply deleted, leading to a 404 Not Found error instead.
- 411 Length Required
- 412 Precondition Failed
- 413 Request Entity Too Large
- 414 Request-URI Too Long
- 415 Unsupported Media Type
- 416 Requested Range Not Satisfiable
- 417 Expectation Failed
- 422 Unprocessable Entity (WebDAV)
- The request was well-formed but was unable to be followed due to semantic errors.
- 423 Locked (WebDAV)
- The resource that is being accessed is locked
- 424 Failed Dependency (WebDAV)
- The request failed due to failure of a previous request (e.g. a PROPPATCH).
- 425 Unordered Collection
- Defined in drafts of WevDav Advanced Collections but not yet implemented.
- 426 Upgrade Required (RFC 2817)
- The client should switch to TLS/1.0.
- 449 Retry With
- A Microsoft extension: The request should be retried after doing the appropriate action.
In the context of a HTTP transaction, the basic authentication scheme is a method designed to allow a web browser, or other client program, to provide credentials – in the form of a user name and password – when making a request. ...
Digest access authentication is one of the agreed methods a web page can use to negotiate credentials with a web user (using the HTTP protocol). ...
...
Micropayments are means for transferring money, in situations where collecting money with the usual payment systems is impractical, or very expensive, in terms of the amount of money being collected. ...
Netscape Navigator displaying the 404 error page at eBay. ...
This article or section does not adequately cite its references or sources. ...
5xx Server Error The server failed to fulfill an apparently valid request. - 500 Internal Server Error
- 501 Not Implemented
- 502 Bad Gateway
- 503 Service Unavailable
- 504 Gateway Timeout
- 505 HTTP Version Not Supported
- 507 Insufficient Storage (WebDAV)
- 509 Bandwidth Limit Exceeded
- This status code, while used by many servers, is not an official HTTP status code.
See also Hypertext Transfer Protocol (HTTP) is a method used to transfer or convey information on the World Wide Web. ...
External links |
Feeds |
Contact