|
| 500 |
Internal Server Error |
The server encountered an unexpected condition which prevented it from
fulfilling the request.
|
| 501 |
Not Implemented |
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.
|
| 502 |
Bad Gateway |
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.
|
| 503 |
Service Unavailable |
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.
|
| 504 |
Gateway Timeout |
The server, while acting as a gateway or proxy, did not receive a timely
response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP)
or some other auxiliary server (e.g. DNS) it needed to access in attempting
to complete the request.
Note: Note to implementors: some deployed proxies are known to
return 400 or 500 when DNS lookups time out.
|
| 505 |
HTTP Version Not Supported |
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, 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.
|
