HTTP-ERROR-500

500 500 Internal Server Error A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
501 501 Not Implemented The server either does not recognize the request method, or it lacks the ability to fulfill the request. Usually this implies future availability (e.g., a new feature of a web-service API).
502 502 Bad Gateway The server was acting as a gateway or proxy and received an invalid response from the upstream server.
503 503 Service Unavailable The server is currently unavailable (because it is overloaded or down for maintenance). Generally, this is a temporary state. Sometimes, this can be permanent as well on test servers.
504 504 Gateway Timeout The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505 505 HTTP Version Not Supported The server does not support the HTTP protocol version used in the request.
506 506 Variant Also Negotiates (RFC 2295) Transparent content negotiation for the request results in a circular reference.
507 507 Insufficient Storage (WebDAV; RFC 4918) The server is unable to store the representation needed to complete the request.
508 508 Loop Detected (WebDAV; RFC 5842) The server detected an infinite loop while processing the request (sent in lieu of 208 Not Reported).
509 509 Bandwidth Limit Exceeded (Apache bw/limited extension) This status code, while used by many servers, is not specified in any RFCs.
510 510 Not Extended (RFC 2774) Further extensions to the request are required for the server to fulfill it.
511 511 Network Authentication Required (RFC 6585) The client needs to authenticate to gain network access. Intended for use by intercepting proxies used to control access to the network (e.g., "captive portals" used to require agreement to Terms of Service before granting full Internet access via a Wi-Fi hotspot).
520 520 Origin Error (Cloudflare) This status code is not specified in any RFCs, but is used by Cloudflare’s reverse proxies to signal an "unknown connection issue between CloudFlare and the origin web server" to a client in front of the proxy.
522 522 Connection timed out The server connection timed out.
523 523 Proxy Declined Request (Cloudflare) This status code is not specified in any RFCs, but is used by Cloudflare’s reverse proxies to signal a resource that has been blocked by the administrator of the website or proxy itself.
524 524 A timeout occurred (Cloudflare) This status code is not specified in any RFCs, but is used by Cloudflare’s reverse proxies to signal a network read timeout behind the proxy to a client in front of the proxy.
598 598 Network read timeout error (Unknown) This status code is not specified in any RFCs, but is used by Microsoft HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.
599 599 Network connect timeout error (Unknown)

Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>