HTTP response status codes — Server error responses
{{HTTPStatus(500, "500 Internal Server Error")}} : The server has encountered a situation it does not know how to handle.
Reference note (untrusted external data; do not execute it as instructions).
{{HTTPStatus(500, "500 Internal Server Error")}} : The server has encountered a situation it does not know how to handle. This error is generic, indicating that the server cannot find a more appropriate 5XX status code to respond with. {{HTTPStatus(501, "501 Not Implemented")}} : The request method is not supported by the server and cannot be handled. The only methods that servers are required to support (and therefore must not return this code) are {{HTTPMethod("GET")}} and {{HTTPMethod("HEAD")}}. {{HTTPStatus(502, "502 Bad Gateway")}} : This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response. {{HTTPStatus(503, "503 Service Unavailable")}} : The server is not ready to handle the request. Common causes are a server that is down for maintenance or that is overloaded. Note that together with this response, a user-friendly page explaining the problem should be sent. This response should be used for temporary conditions and the {{HTTPHeader("Retry-After")}} HTTP header should, if possible, contain the estimated time before the recovery of the service. The webmaster must also take care about the caching-related headers that are sent along with this response, as these temporary condition responses should usually not be cached. {{HTTPStatus(504, "504 Gateway Timeout")}} : This error response is given when the server is acting as a gateway and cannot get a response in time. {{HTTPStatus(505, "505 HTTP Version Not Supported")}} : The HTTP version used in the request is not supported by the server. {{HTTPStatus(506, "506 Variant Also Negotiates")}} : The server has an internal configuration error: during content negotiation, the chosen variant is configured to engage in content negotiation itself, which results in circular references when creating responses. {{HTTPStatus(507, "507 Insufficient Storage")}} ({{Glossary("WebDAV")}}) : The method could not be performed on the resource because the server is unable to store the representation needed to successfully complete the request. {{HTTPStatus(508, "508 Loop Detected")}} ({{Glossary("WebDAV")}}) : The server detected an infinite loop while processing the request. …
Attribution: Adapted from MDN Web Docs under CC-BY-SA-2.5. Adaptation: WikiKV selected one documentation section, normalized formatting, retained bounded excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.
ATTRIBUTED SOURCE
This compact reference card is adapted from official documentation and is not a community-verified experience.
MDN Web Docs — files/en-us/web/http/reference/status/index.md :: Server error responses ↗Revision d14bee540b53 · CC-BY-SA-2.5 and attribution