HTTP Header/Status codes
Sometimes someone needs to know about header codes. Especially while using AJAX.
So I’m posting the codes recently used.
100 => “HTTP/1.1 100 Continue”,
101 => “HTTP/1.1 101 Switching Protocols”,
200 => “HTTP/1.1 200 OK”,
201 => “HTTP/1.1 201 Created”,
202 => “HTTP/1.1 202 Accepted”,
203 => “HTTP/1.1 203 Non-Authoritative Information”,
204 => “HTTP/1.1 204 No Content”,
205 => “HTTP/1.1 205 Reset Content”,
206 => “HTTP/1.1 206 Partial Content”,
300 => “HTTP/1.1 300 Multiple Choices”,
301 => “HTTP/1.1 301 Moved Permanently”,
302 => “HTTP/1.1 302 Found”,
303 => “HTTP/1.1 303 See Other”,
304 => “HTTP/1.1 304 Not Modified”,
305 => “HTTP/1.1 305 Use Proxy”,
307 => “HTTP/1.1 307 Temporary Redirect”,
400 => “HTTP/1.1 400 Bad Request”,
401 => “HTTP/1.1 401 Unauthorized”,
402 => “HTTP/1.1 402 Payment Required”,
403 => “HTTP/1.1 403 Forbidden”,
404 => “HTTP/1.1 404 Not Found”,
405 => “HTTP/1.1 405 Method Not Allowed”,
406 => “HTTP/1.1 406 Not Acceptable”,
407 => “HTTP/1.1 407 Proxy Authentication Required”,
408 => “HTTP/1.1 408 Request Time-out”,
409 => “HTTP/1.1 409 Conflict”,
410 => “HTTP/1.1 410 Gone”,
411 => “HTTP/1.1 411 Length Required”,
412 => “HTTP/1.1 412 Precondition Failed”,
413 => “HTTP/1.1 413 Request Entity Too Large”,
414 => “HTTP/1.1 414 Request-URI Too Large”,
415 => “HTTP/1.1 415 Unsupported Media Type”,
416 => “HTTP/1.1 416 Requested range not satisfiable”,
417 => “HTTP/1.1 417 Expectation Failed”,
500 => “HTTP/1.1 500 Internal Server Error”,
501 => “HTTP/1.1 501 Not Implemented”,
502 => “HTTP/1.1 502 Bad Gateway”,
503 => “HTTP/1.1 503 Service Unavailable”,
504 => “HTTP/1.1 504 Gateway Time-out”
I found more information about the codes. So I’m publishing it here (I need it future). You can read original story from here.
HTTP Status Codes
HTTP Status Code Descriptions – Click Code in List for Details. Details were extracted from RFC’s (Request For Comments) and related documents. To see the RFC use your search engine. These are often on the IETF.org and W3C.org sites.
Note: The two most common status codes on our site are:
403 this normally means you have requested a page that requires registration for access. Register with us on the FrontPage and try again.
404 the page is missing or unavailable right now. We may be updating it temporarily. Try again first. If the problem persists, send us an email reporting it.
100 101 102 103 104
200 201 202 203 204 205 206 207 226
300 301 302 303 304 305 306 307
400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 426
500 501 502 503 504 505 506 507 508 509 510
Status Code Definitions
Each Status-Code is described below, including a description of which methods it can follow and any meta-information required in the response.
1 Informational 1xx
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 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions.
1.1 100 Continue (RFC2616)
The client may 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.
1.2 101 Switching Protocols (RFC2616)
The server understands and is willing to comply with the client’s request, via the Upgrade message header field (section 14.41), for a change in the application protocol being used on this connection. The server will switch protocols to those defined by the response’s Upgrade header field immediately after the empty line which terminates the 101 response.
The protocol should only be switched when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a real-time, synchronous protocol may be advantageous when delivering resources that use such features.
1.3 102 Processing in Progress (RFC2518)
The 102 (Processing) status code is an interim response used to inform the client that the server has accepted the complete request, but has not yet completed it. This status code SHOULD only be sent when the server has a reasonable expectation that the request will take significant time to complete. As guidance, if a method is taking longer than 20 seconds (a reasonable, but arbitrary value) to process the server SHOULD return a 102 (Processing) response. The server MUST send a final response after the request has been completed.
Methods can potentially take a long period of time to process, especially methods that support the Depth header. In such cases the client may time-out the connection while waiting for a response. To prevent this the server may return a 102 (Processing) status code to indicate to the client that the server is still processing the method.
1.4 103 Access denied while creating Web Service
Meaning is installation/implementation dependent.
1.5 104 File Format or Program Error
The program running has an internal format or logic error. For example, comment lines incorrectly delineated. Or the format of a Server Log of configuration file has become corrupted.
2 Successful 2xx
This class of status code indicates that the client’s request was successfully received, understood, and accepted.
2.1 200 OK (RFC2616)
The request has succeeded. The information returned with the response is dependent on the method used in the request, for example:
GET an entity corresponding to the requested resource is sent in the response;
HEAD the entity-header fields corresponding to the requested resource are sent in the response without any message-body;
POST an entity describing or containing the result of the action;
TRACE an entity containing the request message as received by the end server.
2.2 201 Created (RFC2616)
The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URL for the resource given by a Location header field. The origin server MUST create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server should respond with 202 (Accepted) response instead.
2.3 202 Accepted (RFC2616)
The request has been accepted for processing, but the processing 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 re-sending a status code from an asynchronous operation such as this.
The 202 response is intentionally non-committal. Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent’s connection to the server persist until the process is completed. The entity returned with this response SHOULD include an indication of the request’s current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled.
2.4 203 Non-Authoritative Information (RFC2616)
The returned meta-information in the entity-header is not the definitive set as available from the origin server, but is gathered from a local or a third-party copy. The set presented MAY be a subset or superset of the original version. For example, including local annotation information about the resource MAY result in a superset of the meta-information known by the origin server. Use of this response code is not required and is only appropriate when the response would otherwise be 200 (OK).
2.5 204 No Content (RFC2616)
The server has fulfilled the request but there is no new information to send back. If the client is a user agent, it SHOULD NOT change its document view from that which caused the request to be sent. This response is primarily intended to allow input for actions to take place without causing a change to the user agent’s active document view. The response MAY include new meta-information in the form of entity-headers, which SHOULD apply to the document currently in the user agent’s active view.
The 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.
2.6 205 Reset Content (RFC2616)
The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. The response MUST NOT include an entity.
2.7 206 Partial Content (RFC2616)
The server has fulfilled the partial GET request for the resource. The request must have included a Range header field (section 14.36) indicating the desired range. The response MUST include either a Content-Range header field (section 14.17) indicating the range included with this response, or a multipart/byte ranges Content-Type including Content-Range fields for each part. If multipart/byte ranges is not used, the Content-Length header field in the response MUST match the actual number of OCTETs transmitted in the message-body.
A cache that does not support the Range and Content-Range headers MUST NOT cache 206 (Partial) responses.
2.8 207 Multi-status Response (RFC4918)
The default 207 (Multi-Status) response body is a text/xml or application/xml HTTP entity that contains a single XML element called multi-status, which contains a set of XML elements called response which contain 200, 300, 400, and 500 series status codes generated during the method invocation. 100 series status codes SHOULD NOT be recorded in a response XML element.
2.9 226 IM Used (RFC3229)
The IM response-header field is used to indicate the instance-manipulations, if any, that have been applied to the instance represented by the response. Typical instance manipulations include delta encoding and compression. Responses that include an IM header MUST carry a response status code of 226 (IM Used).
3 Redirection 3xx
This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. The action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. A user agent SHOULD NOT automatically redirect a request more than 5 times, since such redirections usually indicate an infinite loop.
3.1 300 Multiple Choices (RFC2616)
The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent-driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice may be performed automatically. However, this specification does not define any standard for such automatic selection.
If the server has a preferred choice of representation, it SHOULD include the specific URL for that representation in the Location field; user agents MAY use the Location field value for automatic redirection. This response is cacheable unless indicated otherwise.
3.2 301 Moved Permanently (RFC2616)
The requested resource has been assigned a new permanent URI and any future references to this resource SHOULD be done using one of the returned URIs. Clients with link editing capabilities SHOULD automatically re-link references to the Request-URI to one or more of the new references returned by the server, where possible. This response is cacheable unless indicated otherwise.
If the new URI is a location, its URL SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity
of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 301 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Note: When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request.
3.3 302 Moved Temporarily (RFC2616)
The requested resource resides temporarily under a different URI. Since the redirection may be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
If the new URI is a location, its URL SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
Note: When automatically redirecting a POST request after receiving a 302 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request.
3.4 303 See Other (RFC2616)
The response to the request can be found under a different URI and SHOULD be retrieved using a GET method on that resource. This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource. The new URI is not a substitute reference for the originally requested resource. The 303 response is not cacheable, but the response to the second (redirected) request MAY be cacheable.
If the new URI is a location, its URL SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s).
3.5 304 Not Modified (RFC2616)
If the client has performed a conditional GET request and access is allowed, but the document has not been modified, the server SHOULD respond with this status code. The response MUST NOT contain a message-body.
The response MUST include the following header fields:
o E Tag and/or Content-Location, if the header would have been sent in a 200 response to the same request
o Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant
If the conditional GET used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers.
If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional.
If a cache uses a received 304 response to update a cache entry, the cache MUST update the entry to reflect any new field values given in the response.
The 304 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields.
3.6 305 Use Proxy (RFC2616)
The requested resource MUST be accessed through the proxy given by the Location field. The Location field gives the URL of the proxy. The recipient is expected to repeat the request via the proxy.
3.7 306 Switch Proxy (RFC2616)
The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved.
3.8 307 Temporarily Redirected (RFC2616)
The requested resource resides temporarily under a different URI. Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s) , since many pre-HTTP/1.1 user agents do not understand the 307 status. Therefore, the note SHOULD contain the information necessary for a user to repeat the original request on the new URI.
If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued.
4 Client Error 4xx
The 4xx class of status code is intended for cases in which the client seems to have erred. Except when responding to a HEAD request, the server SHOULD include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents SHOULD display any included entity to the user.
Note: If the client is sending data, a server implementation using TCP should be careful to ensure that the client acknowledges receipt of the packets) containing the response, before the server closes the input connection. If the client continues sending data to the server after the close, the server’s TCP stack will send a reset packet to the client, which may erase the client’s unacknowledged input buffers before they can be read and interpreted by the HTTP application.
4.1 400 Bad Request (RFC2616)
The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.
4.2 401 Unauthorized (RFC2616)
The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.46) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity MAY include relevant diagnostic information. HTTP access authentication is explained in section 11.
4.3 402 Payment Required (RFC2616)
This code is reserved for future use.
4.4 403 Forbidden (RFC2616)
The server understood the request, but is refusing to fulfill it. Authorization will not help and the request SHOULD NOT be repeated. If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. This status code is commonly used when the server does not wish to reveal exactly why the request has been refused, or when no other response is applicable.
4.5 404 Not Found (RFC2616)
The server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent.
If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address.
4.6 405 Method Not Allowed (RFC2616)
The method specified in the Request-Line is not allowed for the resource identified by the Request-URI. The response MUST include an Allow header containing a list of valid methods for the requested resource.
4.7 406 Not Acceptable (RFC2616)
The resource identified by the request is only capable of generating response entities which have content characteristics not acceptable according to the accept headers sent in the request.
Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. The entity format is specified by the media type given in the Content-Type header field. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice may be performed automatically. However, this specification does not define any standard for such automatic selection.
Note: HTTP/1.1 servers are allowed to return responses which are not acceptable according to the accept headers sent in the request. In some cases, this may even be preferable to sending a 406 response. User agents are encouraged to inspect the headers of an incoming response to determine if it is acceptable. If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions.
4.8 407 Proxy Authentication Required (RFC2616)
This code is similar to 401 (Unauthorized), but indicates that the client MUST first authenticate itself with the proxy. The proxy MUST return a Proxy-Authenticate header field (section 14.33) containing a challenge applicable to the proxy for the requested resource. The client MAY repeat the request with a suitable Proxy-Authorization header field (section 14.34). HTTP access authentication is explained in section 11.
4.9 408 Request Timeout (RFC2616)
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.
4.10 409 Conflict (RFC2616)
The request could not be completed due to a conflict with the current state of the resource. This code is only allowed in situations where it is expected that the user might be able to resolve the conflict and resubmit the request. The response body SHOULD include enough information for the user to recognize the source of the conflict. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that may not be possible and is not required.
Conflicts are most likely to occur in response to a PUT request. If versioning is being used and the entity being PUT includes changes to a resource which conflict with those made by an earlier (third-party) request, the server MAY use the 409 response to indicate that it can’t complete the request. In this case, the response entity SHOULD contain a list of the differences between the two versions in a format defined by the response Content-Type.
4.11 410 Gone (RFC2616)
The requested resource is no longer available at the server and no forwarding address is known. This condition SHOULD be considered permanent. Clients with link editing capabilities SHOULD delete references to the Request-URI after user approval. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. This response is cacheable unless indicated otherwise.
The 410 response is primarily intended to assist the task of web maintenance by notifying the recipient that the resource is intentionally unavailable and that the server owners desire that remote links to that resource be removed. Such an event is common for limited-time, promotional services and for resources belonging to individuals no longer working at the server’s site. It is not necessary to mark all permanently unavailable resources as “gone” or to keep the mark for any length of time — that is left to the discretion of the server owner.
4.12 411 Length Required (RFC2616)
The server refuses to accept the request without a defined Content-Length. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.
4.13 412 Precondition Failed (RFC2616)
The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. This response code allows the client to place preconditions on the current resource meta-information (header field data) and thus prevent the requested method from being applied to a resource other than the one intended.
4.14 413 Request Entity Too Large (RFC2616)
The server is refusing to process a request because the request entity is larger than the server is willing or able to process. The server may close the connection to prevent the client from continuing the request.
If the condition is temporary, the server SHOULD include a Retry-After header field to indicate that it is temporary and after what time the client may try again.
4.15 414 Request-URI Too Long (RFC2616)
The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. This rare condition is only likely to occur when a client has improperly converted a POST request to a GET request with long query information, when the client has descended into a URL “black hole” of redirection (e.g., a redirected URL prefix that points to a suffix of itself), or when the server is under attack by a client attempting to exploit security holes present in some servers using fixed-length buffers for reading or manipulating the Request-URI.
4.16 415 Unsupported Media Type (RFC2616)
The server is refusing to service the request because the entity of the request is in a format not supported by the requested resource for the requested method.
4.17 416 Requested Range not Available (RFC2616)
A server SHOULD return a response with this status code if a request included a Range request-header field, and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.)
When this status code is returned for a byte-range request, the response SHOULD include a Content-Range entity-header field specifying the current length of the selected resource. This response MUST NOT use the multipart/byte ranges content- type.
4.18 417 Expectation Failed
The expectation given in an Expect request-header field (see section 14.20) could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
4.19 418 I’m a Teapot (RFC2324)
Any attempt to brew coffee with a teapot should result in the error code “418 I’m a teapot”. The resulting entity body MAY be short and stout. As defined by IETF memo RFC 2324,.this memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Of British origin, clearly.
4.20 419 Expectation Failed
The expectation given in an “Expect” request-header field could not be met by this server, or, if the server is a proxy, the server has unambiguous evidence that the request could not be met by the next-hop server.
4.21 420 Policy not Fulfilled (WD-http-pep-971121)
The policy for accessing the resource has not been met in the request. The response MUST include a PEP-Info or a C-PEP-Info header field specifying the extensions required by the publishing party for accessing the resource. The server MAY use the for attribute bag to indicate whether the policy applies to other resources.
The client MAY repeat the request using the appropriate extensions). If the initial request already included the extensions requested in the 420 response, then the response indicates that access has been refused for those extension declarations.
If the 420 response contains the same set of extension policies as the prior response, then the client MAY present any entity included in the response to the user, since that entity may include relevant diagnostic information.
Implementers may note the similarity to the way authentication challenges are issued with the 401 (Unauthorized) status-code.
4.22 421 Bad Mapping (WD-http-pep-971121)
The mappings indicated by one or more map attribute bags in the request were not unique and mapped the same header field more than once. The client MAY repeat the request using a new set of mappings if it believes that it can find a unique set of header fields for which the transaction will succeed.
4.23 422 Unprocessable Entity (RFC4918)
The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a 415(Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the contained instructions. For example, this error condition may occur if an XML request body contains well-formed (i.e., syntactically correct), but semantically erroneous, XML instructions.
4.24 423 Entity Locked (RFC4918)
The 423 (Locked) status code means the source or destination resource of a method is locked. This response SHOULD contain an appropriate precondition or post-condition code, such as ‘lock-token-submitted’ or ‘no-conflicting-lock’.
4.25 424 Failed Dependency (RFC2518)
The 424 (Failed Dependency) status code means that the method could not be performed on the resource because the requested action depended on another action and that action failed. For example, if a command in a PROPPATCH method fails then, at minimum, the rest of the commands will also fail with 424 (Failed Dependency).
4.27 426 Update Required (RFC2817)
The Upgrade response header field advertises possible protocol upgrades a server MAY accept. In conjunction with the “426 Upgrade Required” status code, a server can advertise the exact protocol upgrades that a client MUST accept to complete the request. The server MAY include an Upgrade header in any response other than 101 or 426 to indicate a willingness to switch to any (combination) of the protocols listed.
5 Server Error 5xx
Response status codes beginning with the digit “5″ indicate cases in which the server is aware that it has erred or is 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 whether it is a temporary or permanent condition. User agents SHOULD display any included entity to the user. These response codes are applicable to any request method.
5.1 500 Internal Server Error (RFC2616)
The server encountered an unexpected condition which prevented it from fulfilling the request.
5.2 501 Not Implemented (RFC2616)
The server does not support the functionality required to fulfill the request. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource.
5.3 502 Bad Gateway (RFC2616)
The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.
5.4 503 Service Unavailable (RFC2616)
The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The implication is that this is a temporary condition which will be alleviated after some delay. If known, the length of the delay may be indicated in a Retry-After header. If no Retry-After is given, the client SHOULD handle the response as it would for a 500 response.
Note: The existence of the 503 status code does not imply that a server must use it when becoming overloaded. Some servers may wish to simply refuse the connection.
5.5 504 Gateway Timeout (RFC2616)
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server it accessed in attempting to complete the request.
5.6 505 HTTP Version Not Supported (RFC2616)
The server does not support, or refuses to support, the HTTP protocol version that was used in the request message. The server is indicating that it is unable or unwilling to complete the request using the same major version as the client, as described in section 3.1, other than with this error message. The response SHOULD contain an entity describing why that version is not supported and what other protocols are supported by that server.
5.7 506 Variant also negotiates. Not an endpoint (RFC2295)
The 506 status code indicates that the server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
5.8 507 Insufficient Storage (RFC4918)
The 507 (Insufficient Storage) status code means the method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. This condition is considered to be temporary. If the request which received this status code was the result of a user action, the request MUST NOT be repeated until it is requested by a separate user action.
5.9 508 Cross Server Binding Forbidden
Since most servers will be forced to fail cross-server BIND requests because they are unable to guarantee the integrity of cross-server
bindings, status code 508 (Cross-server Binding Forbidden) is defined.
5.10 509 Bandwidth Exceeded
Implementation dependent. The bandwidth available with your ISP or circuit provider has been/or soon will be exceeded. Different thresholds are used. 80 – 90% is common.
5.11 510 Request not Extended. Policy Violation (RFC2774)
The server must identify all mandatory extension declarations (both hop-by-hop and end-to-end); the server MAY ignore optional declarations without affecting the result of processing the HTTP message, and examine all extensions identified to determine if they are supported for this message. If not, respond with a 510
999.0 999 Unknown or Indeterminate
Added by CCS to indicate that available logic and information does not permit isolating the error completely. No additional information is available. Try the page request again. Check Browser, Computer, Server and Communication Software and Equipment conditions.