Server Error (500 Range)
Occasionally, the error might be with the
server itself—or, more commonly, with the CGI portion of the
server. CGI programmers are painfully familiar with the 500 (Internal
Server Error) code, which frequently means that their program
crashed. One error that client programmers should pay attention to is
503 (Service Unavailable), which means that their request cannot be
performed right now, but the Retry-After header
(if supplied) indicates when the client might try again.
The following is a complete listing of response codes implying a server error:
|
Code |
Meaning |
|
500 Internal Server Error |
This code indicates that a part of the server (for example, a CGI program) has crashed or encountered a configuration error. |
|
501 Not Implemented |
This code indicates that the client requested an action that cannot be performed by the server. |
|
502 Bad Gateway |
This code indicates that the server (or proxy) encountered invalid responses from another server (or proxy). |
|
503 Service Unavailable |
This code means that the service is temporarily unavailable, but
should be restored in the future. If the server knows when it will be
available again, a |
|
504 Gateway Time-out |
This response is like 408 (Request Time-out) except that a gateway or proxy has timed out. |
|
505 HTTP Version Not Supported |
The server will not support the HTTP protocol version used in the request. |
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access