I was trying to find an official, authoritative list of HTTP Status Codes but I kept finding lists that weren't authoritative or complete. So I searched and found my answer in the Apache HTTP Server source code. Once I had the exact HTTP Status Codes and resulting Error Documents sent by Apache, I researched deeper into HTTP Status Codes by reading as many related RFC's as I could find, and several other software source codes were explored. This is the most authoritative list I know of, if you can do better leave a comment and I'll update it. Another thing to keep in mind, the Status code number itself is what is used by software and hardware to make determinations, the phrase returned by the status code is for the human only and does not have any weight other than informing the user.. So "503 Service Unavailable", "503 Service Temporarily Unavailable", and "503 Get the heck outta here" are all completely valid.
Update March 9, 2009: A lot of sites on the web have updated their HTTP status code lists to include the HTTP Status codes listed on this page, including Wikipedia, IANA, W3C, and others, so rest assured this info is accurate and complete. If you'd like to see how to create custom error pages for all of these errors like mine /show-error-506 , then check out this detailed tutorial I just posted.
Once I compiled the list of Apache recognized HTTP Status Codes, I was dying to see them all in action (i.e. the corresponding ErrorDocument). At first I thought I would have to create a php or perl script emulating each of the 57 HTTP Status Codes, a tedious undertaking I wasn't about to do. Instead I "asked Apache" by searching the Apache HTTP Documentation for ambiguity sending Status Codes and/or triggering ErrorDocuments with an Apache Directive.
While reading up on mod_alias and the Redirect directive I found:
Apache DocsSyntax: Redirect [status] URL-path URL The status argument can be used to return other HTTP status codes. Other status codes can be returned by giving the numeric status code as the value of status. If the status is between 300 and 399, the URL argument must be present, otherwise it must be omitted.
HTTP_INFO - Request received, continuing process. Indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line.
HTTP_CONTINUEHTTP_SWITCHING_PROTOCOLSHTTP_PROCESSINGHTTP_SUCCESS - The action was successfully received, understood, and accepted. Indicates that the client's request was successfully received, understood, and accepted.
HTTP_OKHTTP_CREATEDHTTP_ACCEPTEDHTTP_NON_AUTHORITATIVEHTTP_NO_CONTENTHTTP_RESET_CONTENTHTTP_PARTIAL_CONTENTHTTP_MULTI_STATUSHTTP_REDIRECT - The client must take additional action to complete the request. 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.
HTTP_MULTIPLE_CHOICESHTTP_MOVED_PERMANENTLYHTTP_MOVED_TEMPORARILYHTTP_SEE_OTHERHTTP_NOT_MODIFIEDHTTP_USE_PROXYUNUSEDHTTP_TEMPORARY_REDIRECTHTTP_CLIENT_ERROR - The request contains bad syntax or cannot be fulfilled. Indicates case where 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.
HTTP_BAD_REQUESTHTTP_UNAUTHORIZEDHTTP_PAYMENT_REQUIREDHTTP_FORBIDDENHTTP_NOT_FOUNDHTTP_METHOD_NOT_ALLOWEDHTTP_NOT_ACCEPTABLEHTTP_PROXY_AUTHENTICATION_REQUIREDHTTP_REQUEST_TIME_OUTHTTP_CONFLICTHTTP_GONEHTTP_LENGTH_REQUIREDHTTP_PRECONDITION_FAILEDHTTP_REQUEST_ENTITY_TOO_LARGEHTTP_REQUEST_URI_TOO_LARGEHTTP_UNSUPPORTED_MEDIA_TYPEHTTP_RANGE_NOT_SATISFIABLEHTTP_EXPECTATION_FAILEDUNUSEDUNUSEDUNUSEDUNUSEDHTTP_UNPROCESSABLE_ENTITYHTTP_LOCKEDHTTP_FAILED_DEPENDENCYHTTP_NO_CODEHTTP_UPGRADE_REQUIREDHTTP_SERVER_ERROR - The server failed to fulfill an apparently valid request. 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.
HTTP_INTERNAL_SERVER_ERRORHTTP_NOT_IMPLEMENTEDHTTP_BAD_GATEWAYHTTP_SERVICE_UNAVAILABLEHTTP_GATEWAY_TIME_OUTHTTP_VERSION_NOT_SUPPORTEDHTTP_VARIANT_ALSO_VARIESHTTP_INSUFFICIENT_STORAGEUNUSEDUNUSEDHTTP_NOT_EXTENDEDLet start with a quick and easy example. Add the following Redirect rules to your htaccess file, then open your browser and goto each url like yoursite.com/e/400. Don't create an /e/ directory or any files.
Redirect 400 /e/400 Redirect 503 /e/503 Redirect 405 /e/405
When a Status code is encountered, Apache outputs the Header and the ErrorDocument for that error code. So you can view any Header and the default ErrorDocument, by causing that numerical error code, which is caused by the Status Code.
For instance, if you request a file that doesn't exist, a 404 Not Found Header is issued and the corresponding ErrorDocument is served with the 404 Not Found Header.
Redirect 100 /e/100 Redirect 101 /e/101 Redirect 102 /e/102 Redirect 200 /e/200 Redirect 201 /e/201 Redirect 202 /e/202 Redirect 203 /e/203 Redirect 204 /e/204 Redirect 205 /e/205 Redirect 206 /e/206 Redirect 207 /e/207 Redirect 300 /e/300 https://www.askapache.com/?s=300 Redirect 301 /e/301 https://www.askapache.com/?s=301 Redirect 302 /e/302 https://www.askapache.com/?s=302 Redirect 303 /e/303 https://www.askapache.com/?s=303 Redirect 304 /e/304 https://www.askapache.com/?s=304 Redirect 305 /e/305 https://www.askapache.com/?s=305 Redirect 306 /e/306 https://www.askapache.com/?s=306 Redirect 307 /e/307 https://www.askapache.com/?s=307 Redirect 400 /e/400 Redirect 401 /e/401 Redirect 402 /e/402 Redirect 403 /e/403 Redirect 404 /e/404 Redirect 405 /e/405 Redirect 406 /e/406 Redirect 407 /e/407 Redirect 408 /e/408 Redirect 409 /e/409 Redirect 410 /e/410 Redirect 411 /e/411 Redirect 412 /e/412 Redirect 413 /e/413 Redirect 414 /e/414 Redirect 415 /e/415 Redirect 416 /e/416 Redirect 417 /e/417 Redirect 418 /e/418 Redirect 419 /e/419 Redirect 420 /e/420 Redirect 421 /e/421 Redirect 422 /e/422 Redirect 423 /e/423 Redirect 424 /e/424 Redirect 425 /e/425 Redirect 426 /e/426 Redirect 500 /e/500 Redirect 501 /e/501 Redirect 502 /e/502 Redirect 503 /e/503 Redirect 504 /e/504 Redirect 505 /e/505 Redirect 506 /e/506 Redirect 507 /e/507 Redirect 508 /e/508 Redirect 509 /e/509 Redirect 510 /e/510
Now all I have to do is add 57 Redirect Directives to my htaccess, and then request each of them 1 at a time from my browser to see the result, and use a packet sniffing program like WireShark to see the Headers. Uh, scratch that, that would take way too long!
Instead I hacked up a simple php script using cURL to automate sending GET Requests to each of the 57 Redirect URL-paths. A side benefit of using the php script is that it performs all 57 Requests concurrently and saves each Requests returned headers and content to an output buffer. After all 57 have been queried, the output buffer is flushed to the browser.
$res)
{
foreach($res as $key)
{
$ch = curl_init("$SITENAME/e/$key");
$fp = fopen ($TMPSAVETO, "a");
curl_setopt ($ch, CURLOPT_FILE, $fp);
curl_setopt ($ch, CURLOPT_FOLLOWLOCATION ,1);
curl_setopt ($ch, CURLOPT_HEADER ,1);
curl_exec ($ch);
curl_close ($ch);
fclose ($fp);
}
}
$OUT='';
ob_start();
header ("Content-Type: text/plain;");
readfile($TMPSAVETO);
$OUT=ob_get_clean();
echo $OUT;
unlink($TMPSAVETO);
exit;
?>
HTTP/1.1 100 Continue100 Continue Continue
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 101 Switching Protocols101 Switching Protocols Switching Protocols
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 102 Processing X-Pad: avoid browser bug102 Processing Processing
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 200 OK200 OK OK
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 201 Created201 Created Created
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 202 Accepted202 Accepted Accepted
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 203 Non-Authoritative Information203 Non-Authoritative Information Non-Authoritative Information
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 204 No Content Content-Type: text/plain; charset=UTF-8
HTTP/1.1 205 Reset Content205 Reset Content Reset Content
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 206 Partial Content206 Partial Content Partial Content
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 207 Multi-Status X-Pad: avoid browser bug207 Multi-Status Multi-Status
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 300 Multiple Choices Location: https://www.askapache.com/?s=300300 Multiple Choices Multiple Choices
HTTP/1.1 301 Moved Permanently Location: https://www.askapache.com/?s=301301 Moved Permanently Moved Permanently
The document has moved here .
HTTP/1.1 302 Found Location: https://www.askapache.com/?s=302302 Found Found
The document has moved here .
HTTP/1.1 303 See Other Location: https://www.askapache.com/?s=303303 See Other See Other
The answer to your request is located here .
HTTP/1.1 304 Not Modified
HTTP/1.1 305 Use Proxy Location: https://www.askapache.com/?s=305305 Use Proxy Use Proxy
This resource is only accessible through the proxy https://www.askapache.com/?s=305
You will need to configure your client to use that proxy.
HTTP/1.1 306 unused Location: https://www.askapache.com/?s=306306 unused unused
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 307 Temporary Redirect Location: https://www.askapache.com/?s=307307 Temporary Redirect Temporary Redirect
The document has moved here .
HTTP/1.1 400 Bad Request Connection: close400 Bad Request Bad Request
Your browser sent a request that this server could not understand.
HTTP/1.1 401 Authorization Required401 Authorization Required Authorization Required
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
HTTP/1.1 402 Payment Required402 Payment Required Payment Required
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 403 Forbidden403 Forbidden Forbidden
You don't have permission to access /e/403 on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
HTTP/1.1 404 Not Found404 Not Found Not Found
The requested URL /e/404 was not found on this server.
NOTE:
You will most definately want to check out and use the Google 404 Error Page if you run WordPress.
HTTP/1.1 405 Method Not Allowed Allow: TRACE405 Method Not Allowed Method Not Allowed
The requested method GET is not allowed for the URL /e/405.
HTTP/1.1 406 Not Acceptable406 Not Acceptable Not Acceptable
An appropriate representation of the requested resource /e/406 could not be found on this server.
HTTP/1.1 407 Proxy Authentication Required407 Proxy Authentication Required Proxy Authentication Required
This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.
HTTP/1.1 408 Request Time-out Connection: close408 Request Time-out Request Time-out
Server timeout waiting for the HTTP request from the client.
HTTP/1.1 409 Conflict409 Conflict Conflict
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 410 Gone410 Gone Gone
The requested resource
/e/410
is no longer available on this server and there is no forwarding address. Please remove all references to this resource.
HTTP/1.1 411 Length Required Connection: close411 Length Required Length Required
A request of the requested method GET requires a valid Content-length.
HTTP/1.1 412 Precondition Failed412 Precondition Failed Precondition Failed
The precondition on the request for the URL /e/412 evaluated to false.
HTTP/1.1 413 Request Entity Too Large Connection: close413 Request Entity Too Large Request Entity Too Large
The requested resource
/e/413
does not allow request data with GET requests, or the amount of data provided in the request exceeds the capacity limit.
HTTP/1.1 414 Request-URI Too Large Connection: close414 Request-URI Too Large Request-URI Too Large
The requested URL's length exceeds the capacity limit for this server.
HTTP/1.1 415 Unsupported Media Type415 Unsupported Media Type Unsupported Media Type
The supplied request data is not in a format acceptable for processing by this resource.
HTTP/1.1 416 Requested Range Not Satisfiable
HTTP/1.1 417 Expectation Failed417 Expectation Failed Expectation Failed
The expectation given in the Expect request-header field could not be met by this server.
The client sent Expect:
HTTP/1.1 418 I'm a teapot418 I'm a teapot I'm a teapot
Unfortunately this coffee machine is out of coffee.
HTTP/1.1 419 unused419 unused unused
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 420 unused420 unused unused
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 421 unused421 unused unused
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 422 Unprocessable Entity422 Unprocessable Entity Unprocessable Entity
The server understands the media type of the request entity, but was unable to process the contained instructions.
HTTP/1.1 423 Locked423 Locked Locked
The requested resource is currently locked. The lock must be released or proper identification given before the method can be applied.
HTTP/1.1 424 Failed Dependency424 Failed Dependency Failed Dependency
The method could not be performed on the resource because the requested action depended on another action and that other action failed.
HTTP/1.1 425 No code425 No code No code
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 426 Upgrade Required426 Upgrade Required Upgrade Required
The requested resource can only be retrieved using SSL. The server is willing to upgrade the current connection to SSL, but your client doesn't support it. Either upgrade your client, or try requesting the page using https://
HTTP/1.1 500 Internal Server Error Connection: close500 Internal Server Error Internal Server Error
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
HTTP/1.1 501 Method Not Implemented Allow: TRACE Connection: close501 Method Not Implemented Method Not Implemented
GET to /e/501 not supported.
HTTP/1.1 502 Bad Gateway X-Pad: avoid browser bug502 Bad Gateway Bad Gateway
The proxy server received an invalid response from an upstream server.
HTTP/1.1 503 Service Temporarily Unavailable Connection: close503 Service Temporarily Unavailable Service Temporarily Unavailable
The server is temporarily unable to service your request due to maintenance downtime or capacity problems. Please try again later.
HTTP/1.1 504 Gateway Time-out504 Gateway Time-out Gateway Time-out
The proxy server did not receive a timely response from the upstream server.
HTTP/1.1 505 HTTP Version Not Supported505 HTTP Version Not Supported HTTP Version Not Supported
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 506 Variant Also Negotiates506 Variant Also Negotiates Variant Also Negotiates
A variant for the requested resource <pre> /e/506 </pre> is itself a negotiable resource. This indicates a configuration error.
HTTP/1.1 507 Insufficient Storage507 Insufficient Storage Insufficient Storage
The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. There is insufficient free space left in your storage allocation.
HTTP/1.1 508 unused508 unused unused
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 509 unused509 unused unused
The server encountered an internal error or misconfigurationand was unable to complete your request.
Please contact the server administrator, SERVER_ADMIN and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
HTTP/1.1 510 Not Extended X-Pad: avoid browser bug510 Not Extended Not Extended
A mandatory extension policy in the request is not accepted by the server for this resource.
From httpd.h
/** * The size of the static array in http_protocol.c for storing * all of the potential response status-lines (a sparse table). * A future version should dynamically generate the apr_table_t at startup. */ #define RESPONSE_CODES 57 #define HTTP_CONTINUE 100 #define HTTP_SWITCHING_PROTOCOLS 101 #define HTTP_PROCESSING 102 #define HTTP_OK 200 #define HTTP_CREATED 201 #define HTTP_ACCEPTED 202 #define HTTP_NON_AUTHORITATIVE 203 #define HTTP_NO_CONTENT 204 #define HTTP_RESET_CONTENT 205 #define HTTP_PARTIAL_CONTENT 206 #define HTTP_MULTI_STATUS 207 #define HTTP_MULTIPLE_CHOICES 300 #define HTTP_MOVED_PERMANENTLY 301 #define HTTP_MOVED_TEMPORARILY 302 #define HTTP_SEE_OTHER 303 #define HTTP_NOT_MODIFIED 304 #define HTTP_USE_PROXY 305 #define HTTP_TEMPORARY_REDIRECT 307 #define HTTP_BAD_REQUEST 400 #define HTTP_UNAUTHORIZED 401 #define HTTP_PAYMENT_REQUIRED 402 #define HTTP_FORBIDDEN 403 #define HTTP_NOT_FOUND 404 #define HTTP_METHOD_NOT_ALLOWED 405 #define HTTP_NOT_ACCEPTABLE 406 #define HTTP_PROXY_AUTHENTICATION_REQUIRED 407 #define HTTP_REQUEST_TIME_OUT 408 #define HTTP_CONFLICT 409 #define HTTP_GONE 410 #define HTTP_LENGTH_REQUIRED 411 #define HTTP_PRECONDITION_FAILED 412 #define HTTP_REQUEST_ENTITY_TOO_LARGE 413 #define HTTP_REQUEST_URI_TOO_LARGE 414 #define HTTP_UNSUPPORTED_MEDIA_TYPE 415 #define HTTP_RANGE_NOT_SATISFIABLE 416 #define HTTP_EXPECTATION_FAILED 417 #define HTTP_UNPROCESSABLE_ENTITY 422 #define HTTP_LOCKED 423 #define HTTP_FAILED_DEPENDENCY 424 #define HTTP_UPGRADE_REQUIRED 426 #define HTTP_INTERNAL_SERVER_ERROR 500 #define HTTP_NOT_IMPLEMENTED 501 #define HTTP_BAD_GATEWAY 502 #define HTTP_SERVICE_UNAVAILABLE 503 #define HTTP_GATEWAY_TIME_OUT 504 #define HTTP_VERSION_NOT_SUPPORTED 505 #define HTTP_VARIANT_ALSO_VARIES 506 #define HTTP_INSUFFICIENT_STORAGE 507 #define HTTP_NOT_EXTENDED 510 /** is the status code informational */ #define ap_is_HTTP_INFO(x) (((x) >= 100)&&((x) < 200)) /** is the status code OK ?*/ #define ap_is_HTTP_SUCCESS(x) (((x) >= 200)&&((x) < 300)) /** is the status code a redirect */ #define ap_is_HTTP_REDIRECT(x) (((x) >= 300)&&((x) < 400)) /** is the status code a error (client or server) */ #define ap_is_HTTP_ERROR(x) (((x) >= 400)&&((x) < 600)) /** is the status code a client error */ #define ap_is_HTTP_CLIENT_ERROR(x) (((x) >= 400)&&((x) < 500)) /** is the status code a server error */ #define ap_is_HTTP_SERVER_ERROR(x) (((x) >= 500)&&((x) < 600)) /** is the status code a (potentially) valid response code? */ #define ap_is_HTTP_VALID_RESPONSE(x) (((x) >= 100)&&((x) < 600)) /** should the status code drop the connection */ #define ap_status_drops_connection(x) (((x) == HTTP_BAD_REQUEST) || ((x) == HTTP_REQUEST_TIME_OUT) || ((x) == HTTP_LENGTH_REQUIRED) || ((x) == HTTP_REQUEST_ENTITY_TOO_LARGE) || ((x) == HTTP_REQUEST_URI_TOO_LARGE) || ((x) == HTTP_INTERNAL_SERVER_ERROR) || ((x) == HTTP_SERVICE_UNAVAILABLE) || ((x) == HTTP_NOT_IMPLEMENTED))
Is the status code (x) informational?
x >= 100 && x < 200
Is the status code (x) OK?
x >= 200 && x < 300
Is the status code (x) a redirect?
x >= 300 && x < 400
Is the status code (x) a error (client or server)?
x >= 400 && x < 600
Is the status code (x) a client error?
x >= 400 && x < 500
Is the status code (x) a server error?
x >= 500 && x < 600
Is the status code (x) a (potentially) valid response code?
x >= 100 && x < 600
From http_protocol.c
static const char * status_lines[RESPONSE_CODES] = static const char * const status_lines[RESPONSE_CODES] = "100 Continue", "101 Switching Protocols", "102 Processing", "200 OK", "201 Created", "202 Accepted", "203 Non-Authoritative Information", "204 No Content", "205 Reset Content", "206 Partial Content", "207 Multi-Status", "300 Multiple Choices", "301 Moved Permanently", "302 Found", "303 See Other", "304 Not Modified", "305 Use Proxy", "306 unused", "307 Temporary Redirect", "400 Bad Request", "401 Authorization Required", "402 Payment Required", "403 Forbidden", "404 Not Found", "405 Method Not Allowed", "406 Not Acceptable", "407 Proxy Authentication Required", "408 Request Time-out", "409 Conflict", "410 Gone", "411 Length Required", "412 Precondition Failed", "413 Request Entity Too Large", "414 Request-URI Too Large", "415 Unsupported Media Type", "416 Requested Range Not Satisfiable", "417 Expectation Failed", "418 unused", "419 unused", "420 unused", "421 unused", "422 Unprocessable Entity", "423 Locked", "424 Failed Dependency", "425 No code", "426 Upgrade Required", "500 Internal Server Error", "501 Method Not Implemented", "502 Bad Gateway", "503 Service Temporarily Unavailable", "504 Gateway Time-out", "505 HTTP Version Not Supported", "506 Variant Also Negotiates", "507 Insufficient Storage", "508 unused", "509 unused", "510 Not Extended"
| Value | Description | Reference |
|---|---|---|
| 100 | Continue | [RFC2616] , Section 10.1.1 |
| 101 | Switching Protocols | [RFC2616] , Section 10.1.2 |
| 102 | Processing | [RFC2518] , Section 10.1 |
| 200 | OK | [RFC2616] , Section 10.2.1 |
| 201 | Created | [RFC2616] , Section 10.2.2 |
| 202 | Accepted | [RFC2616] , Section 10.2.3 |
| 203 | Non-Authoritative Information | [RFC2616] , Section 10.2.4 |
| 204 | No Content | [RFC2616] , Section 10.2.5 |
| 205 | Reset Content | [RFC2616] , Section 10.2.6 |
| 206 | Partial Content | [RFC2616] , Section 10.2.7 |
| 207 | Multi-Status | [RFC4918] , Section 11.1 |
| 226 | IM Used | [RFC3229] , Section 10.4.1 |
| 300 | Multiple Choices | [RFC2616] , Section 10.3.1 |
| 301 | Moved Permanently | [RFC2616] , Section 10.3.2 |
| 302 | Found | [RFC2616] , Section 10.3.3 |
| 303 | See Other | [RFC2616] , Section 10.3.4 |
| 304 | Not Modified | [RFC2616] , Section 10.3.5 |
| 305 | Use Proxy | [RFC2616] , Section 10.3.6 |
| 306 | (Reserved) | [RFC2616] , Section 10.3.7 |
| 307 | Temporary Redirect | [RFC2616] , Section 10.3.8 |
| 400 | Bad Request | [RFC2616] , Section 10.4.1 |
| 401 | Unauthorized | [RFC2616] , Section 10.4.2 |
| 402 | Payment Required | [RFC2616] , Section 10.4.3 |
| 403 | Forbidden | [RFC2616] , Section 10.4.4 |
| 404 | Not Found | [RFC2616] , Section 10.4.5 |
| 405 | Method Not Allowed | [RFC2616] , Section 10.4.6 |
| 406 | Not Acceptable | [RFC2616] , Section 10.4.7 |
| 407 | Proxy Authentication Required | [RFC2616] , Section 10.4.8 |
| 408 | Request Timeout | [RFC2616] , Section 10.4.9 |
| 409 | Conflict | [RFC2616] , Section 10.4.10 |
| 410 | Gone | [RFC2616] , Section 10.4.11 |
| 411 | Length Required | [RFC2616] , Section 10.4.12 |
| 412 | Precondition Failed | [RFC2616] , Section 10.4.13 |
| 413 | Request Entity Too Large | [RFC2616] , Section 10.4.14 |
| 414 | Request-URI Too Long | [RFC2616] , Section 10.4.15 |
| 415 | Unsupported Media Type | [RFC2616] , Section 10.4.16 |
| 416 | Requested Range Not Satisfiable | [RFC2616] , Section 10.4.17 |
| 417 | Expectation Failed | [RFC2616] , Section 10.4.18 |
| 422 | Unprocessable Entity | [RFC4918] , Section 11.2 |
| 423 | Locked | [RFC4918] , Section 11.3 |
| 424 | Failed Dependency | [RFC4918] , Section 11.4 |
| 426 | Upgrade Required | [RFC2817] , Section 6 |
| 500 | Internal Server Error | [RFC2616] , Section 10.5.1 |
| 501 | Not Implemented | [RFC2616] , Section 10.5.2 |
| 502 | Bad Gateway | [RFC2616] , Section 10.5.3 |
| 503 | Service Unavailable | [RFC2616] , Section 10.5.4 |
| 504 | Gateway Timeout | [RFC2616] , Section 10.5.5 |
| 505 | HTTP Version Not Supported | [RFC2616] , Section 10.5.6 |
| 506 | Variant Also Negotiates | [RFC2295] , Section 8.1 |
| 507 | Insufficient Storage | [RFC4918] , Section 11.5 |
| 510 | Not Extended | [RFC2774] , Section 7 |
I just learned that my modification to the WordPress core was accepted and will be implemented for version 2.8! This may mean WordPress is the only 100% HTTP/1.1 compliant software on the net! Below is the new list (I thought someone out there could use the php array) and as you can see, unfortunately418 I'm a teapotdidn't make it ;)
$wp_header_to_desc = array( 100 => 'Continue', 101 => 'Switching Protocols', 102 => 'Processing', 200 => 'OK', 201 => 'Created', 202 => 'Accepted', 203 => 'Non-Authoritative Information', 204 => 'No Content', 205 => 'Reset Content', 206 => 'Partial Content', 207 => 'Multi-Status', 226 => 'IM Used', 300 => 'Multiple Choices', 301 => 'Moved Permanently', 302 => 'Found', 303 => 'See Other', 304 => 'Not Modified', 305 => 'Use Proxy', 306 => 'Reserved', 307 => 'Temporary Redirect', 400 => 'Bad Request', 401 => 'Unauthorized', 402 => 'Payment Required', 403 => 'Forbidden', 404 => 'Not Found', 405 => 'Method Not Allowed', 406 => 'Not Acceptable', 407 => 'Proxy Authentication Required', 408 => 'Request Timeout', 409 => 'Conflict', 410 => 'Gone', 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', 423 => 'Locked', 424 => 'Failed Dependency', 426 => 'Upgrade Required', 500 => 'Internal Server Error', 501 => 'Not Implemented', 502 => 'Bad Gateway', 503 => 'Service Unavailable', 504 => 'Gateway Timeout', 505 => 'HTTP Version Not Supported', 506 => 'Variant Also Negotiates', 507 => 'Insufficient Storage', 510 => 'Not Extended' );
All the status codes are standard HTTP codes ( http://www.iana.org/assignments/http-status-codes ).
Clients should avoid any form of coupling with the the text/plain error message contained in response body since it may change between different releases of the API and is only intended as a starting point for indentifying the real causes of the exception event.
The following table gives a brief description of the mapping between standard Whois V.3 responses and the related REST services status codes. Consider this table as just an example of the error mapping strategy, it may change with future releases.
| System Exception | Whois Error | HTTP Status Code |
|---|---|---|
| IllegalArgumentException | Bad Request (400) | |
| IllegalStateException | Internal Server Error (500) | |
| UnsupportedOperationException | Bad Request (400) | |
| ObjectNotFoundException | Not Found (404) | |
| IllegalStateException | Bad Request (400) | |
| IOException | Bad Request (400) | |
| SystemException | Internal Server Error (500) | |
| TooManyResultsException | Internal Server Error (500) | |
| WhoisServerException | No Entries Found (101) | Not Found (404) |
| WhoisServerException | Unknown Source (102) | Bad Request (400) |
| WhoisServerException | Unknown Object Type (103) | Bad Request (400) |
| WhoisServerException | Unknown Attribute in Query (104) | Bad Request (400) |
| WhoisServerException | Attribute Is Not Inverse Searchable (105) | Bad Request (400) |
| WhoisServerException | No Search Key Specified (106) | Bad Request (400) |
| WhoisServerException | Access Denied (201) | Forbidden (403) |
| WhoisServerException | Access Control Limit Reached (202) | Forbidden (403) |
| WhoisServerException | Address Passing Not Allowed (203) | Bad Request (400) |
| WhoisServerException | Maximum Referral Lines Exceeded (204) | Internal Server Error (500) |
| WhoisServerException | Connection Has Been Closed(301) | Internal Server Error (500) |
| WhoisServerException | Referral Timeout (302) | Internal Server Error (500) |
| WhoisServerException | No Referral Host (303) | Internal Server Error (500) |
| WhoisServerException | Referral Host Not Responding (304) | Internal Server Error (500) |
Clients will have to define error messages generic enough to represent the four main error conditions, that are Bad Request, Forbidden, Not Found and Internal Server Error.
For example a possible mapping for client side error messages may be:
| HTTP Status Code | Error Message |
|---|---|
| Bad Request (400) | The service is unable to understand and process the query. |
| Forbidden (403) | Query limit exceeded. |
| Not Found (404) | No results were found for Your search "Search term" |
| Internal Server Error (500) | The server encountered an unexpected condition which prevented it from fulfilling the request. |