407 Proxy Authentication Required
408 Request Timeout
The server timed out waiting for the
request. According to W3 HTTP specifications: "The client did not produce
a request within the time that the server was prepared to wait. The client MAY
repeat the request without modifications at any later time."
409 Conflict
Indicates that the request could not be
processed because of conflict in the request, such as an edit conflict.
410 Gone
Indicates that the resource requested is no
longer available and will not be available again. This should be used when a
resource has been intentionally removed; however, it is not necessary to return
this code and a 404 Not Found can be issued instead. However, despite the most
common status code for such a page being 404 Not Found, 410 Gone is still used
by some servers, including Geocities. Upon receiving a 410 status code, the
client should not request the resource again in the future. Clients such as
search engines should remove the resource from their indices.
411 Length Required
The request did not specify the length of
its content, which is required by the requested resource.
412 Precondition Failed
The server does not meet one of the
preconditions that the requester put on the request.
413 Request Entity Too Large
The request is larger than the server is
willing or able to process.
414 Request-URI Too Long
The URI provided was too long for the
server to process.
415 Unsupported Media Type
The request entity has a media type which
the server or resource does not support. For example the client uploads an
image as image/svg+xml, but the server requires that images use a different
format.
416 Requested Range Not
Satisfiable
The client has asked for a portion of the
file, but the server cannot supply that portion. For example, if the client
asked for a part of the file that lies beyond the end of the file.
417 Expectation Failed
The server cannot meet the requirements of
the Expect request-header field.
418 I'm a teapot
This code was defined as one of the
traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control
Protocol, and is not expected to be implemented by actual HTTP servers.
422 Unprocessable Entity (WebDAV)
(RFC 4918)
The request was well-formed but was unable
to be followed due to semantic errors.
423 Locked (WebDAV) (RFC 4918)
The resource that is being accessed is locked
424 Failed Dependency (WebDAV)
(RFC 4918)
The request failed due to failure of a
previous request (e.g. a PROPPATCH).
425 Unordered Collection (RFC
3648)
Defined in drafts of "WebDAV Advanced
Collections Protocol",[8] but not present in "Web Distributed
Authoring and Versioning (WebDAV) Ordered Collections Protocol".[9]
426 Upgrade Required (RFC 2817)
The client should switch to a different
protocol such as TLS/1.0.[10]
449 Retry With
A Microsoft extension. The request should
be retried after doing the appropriate action.[11]
450 Blocked by Windows Parental
Controls
A Microsoft extension. This error is given
when Windows Parental Controls are turned on and are blocking access to the
given webpage.[12]
5xx Server Error
The
server failed to fulfill an apparently valid request.
Response
status codes beginning with the digit "5" indicate cases in which the
server is aware that it has encountered an error or is otherwise incapable of
performing the request. Except when responding to a HEAD request, the server
should include an entity containing an explanation of the error situation, and
indicate whether it is a temporary or permanent condition. Likewise, user
agents should display any included entity to the user. These response codes are
applicable to any request method.
500 Internal Server Error
A generic error message, given when no more
specific message is suitable.
501 Not Implemented
The server either does not recognise the
request method, or it lacks the ability to fulfill the request.
502 Bad Gateway
The server was acting as a gateway or proxy
and received an invalid response from the upstream server.
503 Service Unavailable
The server is currently unavailable
(because it is overloaded or down for maintenance). Generally, this is a
temporary state.
504 Gateway Timeout
The server was acting as a gateway or proxy
and did not receive a timely response from the upstream server.
505 HTTP Version Not Supported
The server does not support the HTTP
protocol version used in the request.
506 Variant Also Negotiates (RFC
2295)
Transparent content negotiation for the
request, results in a circular reference.
507 Insufficient Storage (WebDAV)
(RFC 4918)
509 Bandwidth Limit Exceeded (Apache
bw/limited extension)
This status code, while used by many
servers, is not specified in any RFCs.
510 Not Extended (RFC 2774)
Further extensions to the request are
required for the server to fulfill it.
Posts
0 comments:
Post a Comment