5xx Server Error Responses Subtopics
Explore concepts and entries related to 5xx Server Error Responses.
500 Internal Server Error
The HTTP 500 Internal Server Error status code indicates that the server encountered an unexpected condition that prevented it from completing a request. Learn what causes 500 errors and how DevOps engineers troubleshoot them.
501 Not Implemented
The HTTP 501 Not Implemented status code indicates that the server does not support the functionality required to complete the request.
502 Bad Gateway
The HTTP 502 Bad Gateway status code indicates that a server acting as a gateway or proxy received an invalid response from an upstream server.
503 Service Unavailable
The HTTP 503 Service Unavailable status code indicates that a server is temporarily unable to handle a request. Learn how maintenance, scaling issues, and outages cause 503 errors.
504 Gateway Timeout
The HTTP 504 Gateway Timeout status code indicates that a gateway or proxy did not receive a response from an upstream server within the expected time.
505 HTTP Version Not Supported
The HTTP 505 Version Not Supported status code indicates that the server does not support the HTTP protocol version used in the request.
506 Variant Also Negotiates
The HTTP 506 Variant Also Negotiates status code indicates that the server configuration contains an internal negotiation error.
507 Insufficient Storage
The HTTP 507 Insufficient Storage status code indicates that the server cannot store the information required to complete the request.
508 Loop Detected
The HTTP 508 Loop Detected status code indicates that the server detected an infinite loop while processing a request.
510 Not Extended
The HTTP 510 Not Extended status code indicates that additional extensions are required for the server to fulfil the request.
511 Network Authentication Required
The HTTP 511 Network Authentication Required status code indicates that the client must authenticate with the network before accessing the requested resource.