SEO

May 13, 2019

5xx Server errors


A 404 error on Wikipedia.




5xx Server errors






This class of status code is intended for situations in which the error seems to have been caused by the client. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and whether it is a temporary or permanent condition. These status codes are applicable to any request method. User agents should display any included entity to the user.[31]





400 Bad Request
The server cannot or will not process the request due to an apparent client error (e.g., malformed request syntax, size too large, invalid request message framing, or deceptive request routing).[32]
401 Unauthorized (RFC 7235)
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided. The response must include a WWW-Authenticate header field containing a challenge applicable to the requested resource. See Basic access authentication and Digest access authentication.[33] 401 semantically means "unauthenticated",[34] i.e. the user does not have the necessary credentials.
Note: Some sites incorrectly issue HTTP 401 when an IP address is banned from the website (usually the website domain) and that specific address is refused permission to access a website.
402 Payment Required
Reserved for future use. The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, as proposed for example by GNU Taler[35], but that has not yet happened, and this code is not usually used. Google Developers API uses this status if a particular developer has exceeded the daily limit on requests.[36] Sipgate uses this code if an account does not have sufficient funds to start a call.[37] Shopify uses this code when the store has not paid their fees and is temporarily disabled. [38]
403 Forbidden
The request was valid, but the server is refusing action. The user might not have the necessary permissions for a resource, or may need an account of some sort.
404 Not Found
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
405 Method Not Allowed
A request method is not supported for the requested resource; for example, a GET request on a form that requires data to be presented via POST, or a PUT request on a read-only resource.
406 Not Acceptable
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.[39] See Content negotiation.
407 Proxy Authentication Required (RFC 7235)
The client must first authenticate itself with the proxy.[40]
408 Request Timeout
The server timed out waiting for the request. According to HTTP specifications: "The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time."[41]
409 Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource, such as an edit conflict between multiple simultaneous updates.
410 Gone
Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource in the future. Clients such as search engines should remove the resource from their indices.[42] Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.
411 Length Required
The request did not specify the length of its content, which is required by the requested resource.[43]
412 Precondition Failed (RFC 7232)
The server does not meet one of the preconditions that the requester put on the request.[44]
413 Payload Too Large (RFC 7231)
The request is larger than the server is willing or able to process. Previously called "Request Entity Too Large".[45]
414 URI Too Long (RFC 7231)
The URI provided was too long for the server to process. Often the result of too much data being encoded as a query-string of a GET request, in which case it should be converted to a POST request.[46] Called "Request-URI Too Long" previously.[47]
415 Unsupported Media Type (RFC 7231)
The request entity has a media type which the server or resource does not support. For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format.[48]
416 Range Not Satisfiable (RFC 7233)
The client has asked for a portion of the file (byte serving), but the server cannot supply that portion. For example, if the client asked for a part of the file that lies beyond the end of the file.[49] Called "Requested Range Not Satisfiable" previously.[50]
417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.[51]
418 I'm a teapot (RFC 2324, RFC 7168)
This code was defined in 1998 as one of the traditional IETF April Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is not expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.[52] This HTTP status is used as an Easter egg in some websites, including Google.com.[53][54]
421 Misdirected Request (RFC 7540)
The request was directed at a server that is not able to produce a response[55] (for example because of connection reuse).[56]
422 Unprocessable Entity (WebDAV; RFC 4918)
The request was well-formed but was unable to be followed due to semantic errors.[17]
423 Locked (WebDAV; RFC 4918)
The resource that is being accessed is locked.[17]
424 Failed Dependency (WebDAV; RFC 4918)
The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).[17]
425 Too Early (RFC 8470)
Indicates that the server is unwilling to risk processing a request that might be replayed.
426 Upgrade Required
The client should switch to a different protocol such as TLS/1.0, given in the Upgrade header field.[57]
428 Precondition Required (RFC 6585)
The origin server requires the request to be conditional. Intended to prevent the 'lost update' problem, where a client GETs a resource's state, modifies it, and PUTs it back to the server, when meanwhile a third party has modified the state on the server, leading to a conflict.[58]
429 Too Many Requests (RFC 6585)
The user has sent too many requests in a given amount of time. Intended for use with rate-limiting schemes.[58]
431 Request Header Fields Too Large (RFC 6585)
The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large.[58]
451 Unavailable For Legal Reasons (RFC 7725)
A server operator has received a legal demand to deny access to a resource or to a set of resources that includes the requested resource.[59] The code 451 was chosen as a reference to the novel Fahrenheit 451 (see the Acknowledgements in the RFC).



5xx Server errors


The server failed to fulfill a request.
[60]

Response status codes beginning with the digit "5" indicate cases in which the server is aware that it has encountered an error or is otherwise incapable of performing the request. Except when responding to a HEAD request, the server should include an entity containing an explanation of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display any included entity to the user. These response codes are applicable to any request method.[61]

500 Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.[62]
501 Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request. Usually this implies future availability (e.g., a new feature of a web-service API).[63]
502 Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.[64]
503 Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.[65]
504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.[66]
505 HTTP Version Not Supported
The server does not support the HTTP protocol version used in the request.[67]
506 Variant Also Negotiates (RFC 2295)
Transparent content negotiation for the request results in a circular reference.[68]
507 Insufficient Storage (WebDAV; RFC 4918)
The server is unable to store the representation needed to complete the request.[17]
508 Loop Detected (WebDAV; RFC 5842)
The server detected an infinite loop while processing the request (sent instead of 208 Already Reported).
510 Not Extended (RFC 2774)
Further extensions to the request are required for the server to fulfil it.[69]
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).[58]





  1. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content". IETF. Retrieved December 16, 2017.
  2. ^ Jump up to: a b c "Hypertext Transfer Protocol (HTTP) Status Code Registry". Iana.org. Retrieved January 8, 2015.
  3. ^ "The HTTP status codes in IIS 7.0". Microsoft. July 14, 2009. Retrieved April 1, 2009.
  4. ^ "10 Status Code Definitions". W3. Retrieved October 16, 2015.
  5. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content - 5.1.1. Expect". Retrieved September 27, 2017.
  6. ^ "101". httpstatus. Retrieved October 16, 2015.
  7. ^ Goland, Yaronn; Whitehead, Jim; Faizi, Asad; Carter, Steve R.; Jensen, Del (February 1999). HTTP Extensions for Distributed Authoring – WEBDAV. IETF. doi:10.17487/RFC2518. RFC 2518. Retrieved October 24, 2009.
  8. ^ Oku, Kazuho (December 2017). An HTTP Status Code for Indicating Hints. IETF. doi:10.17487/RFC8297. RFC 8297. Retrieved December 20, 2017.
  9. ^ "200 OK". Hypertext Transfer Protocol -- HTTP/1.1. IETF. June 1999. sec. 10.2.1. doi:10.17487/RFC2616. RFC 2616. Retrieved August 30, 2016.
  10. ^ Stewart, Mark; djna. "Create request with POST, which response codes 200 or 201 and content". Stack Overflow. Retrieved October 16, 2015.
  11. ^ "202". httpstatus. Retrieved October 16, 2015.
  12. ^ "RFC 7231, Section 6.3.4".
  13. ^ "RFC 7230, Section 5.7.2".
  14. ^ Simmance, Chris. "Server Response Codes And What They Mean". koozai. Retrieved October 16, 2015.
  15. ^ "IETF RFC7231 section 6.3.6. - 205 Reset Content". IETF.org. Retrieved September 6, 2018.
  16. ^ "diff --git a/linkchecker.module b/linkchecker.module". Drupal. Retrieved October 16, 2015.
  17. ^ Jump up to: a b c d e Dusseault, Lisa, ed. (June 2007). HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV). IETF. doi:10.17487/RFC4918. RFC 4918. Retrieved October 24, 2009.
  18. ^ Delta encoding in HTTP. IETF. January 2002. doi:10.17487/RFC3229. RFC 3229. Retrieved February 25, 2011.
  19. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content". IETF. Retrieved February 13, 2016.
  20. ^ "300". httpstatus. Retrieved October 16, 2015.
  21. ^ "301". httpstatus. Retrieved October 16, 2015.
  22. ^ Berners-Lee, Tim; Fielding, Roy T.; Nielsen, Henrik Frystyk (May 1996). Hypertext Transfer Protocol – HTTP/1.0. IETF. doi:10.17487/RFC1945. RFC 1945. Retrieved October 24, 2009.
  23. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 6.4". IETF. Retrieved June 12, 2014.
  24. ^ "Reference of method redirect_to in Ruby Web Framework "Ruby on Rails". It states: The redirection happens as a "302 Moved" header unless otherwise specified". Retrieved June 30, 2012.
  25. ^ "303". httpstatus. Retrieved October 16, 2015.
  26. ^ "304 Not Modified". Mozilla Developer Network. Retrieved July 6, 2017.
  27. ^ "Mozilla Bugzilla Bug 187996: Strange behavior on 305 redirect, comment 13". March 3, 2003. Retrieved May 21, 2009.
  28. ^ Cohen, Josh. "HTTP/1.1 305 and 306 Response Codes". HTTP Working Group.
  29. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 6.4.7 307 Temporary Redirect". IETF. 2014. Retrieved September 20, 2014.
  30. ^ "The Hypertext Transfer Protocol Status Code 308 (Permanent Redirect)". Internet Engineering Task Force. April 2015. Retrieved April 6, 2015.
  31. ^ "E Explanation of Failure Codes". Oracle. Retrieved October 16, 2015.
  32. ^ "RFC7231 on code 400". Tools.ietf.org. Retrieved January 8, 2015.
  33. ^ "401". httpstatus. Retrieved October 16, 2015.
  34. ^ "RFC7235 on code 401". Tools.ietf.org. Retrieved February 8, 2015.
  35. ^ "The GNU Taler tutorial for PHP Web shop developers 0.4.0". docs.taler.net. Retrieved October 29, 2017.
  36. ^
    "Google API Standard Error Responses". 2016. Retrieved June 21, 2017.
  37. ^ "Sipgate API Documentation". Retrieved July 10, 2018.
  38. ^ "Shopify Documentation". Retrieved July 25, 2018.
  39. ^ Singh, Prabhat; user1740567. "Spring 3.x JSON status 406 "characteristics not acceptable according to the request "accept" headers ()"". Stack Overflow. Retrieved October 16, 2015.
  40. ^ "407". httpstatus. Retrieved October 16, 2015.
  41. ^ "408". httpstatus. Retrieved October 16, 2015.
  42. ^
    "Does Google treat 404 and 410 status codes differently? (Youtube)". 2014. Retrieved February 4, 2015.
  43. ^ "List of HTTP status codes". Google Books. Retrieved October 16, 2015.
  44. ^ Kowser; Patel, Amit. "REST response code for invalid data". Stack Overflow. Retrieved October 16, 2015.
  45. ^ "RFC2616 on status 413". Tools.ietf.org. Retrieved November 11, 2015.
  46. ^ user27828. "GET Request - Why is my URI so long?". Stack Overflow. Retrieved October 16, 2015.
  47. ^ "RFC2616 on status 414". Tools.ietf.org. Retrieved November 11, 2015.
  48. ^ "RFC7231 on status 415". Tools.ietf.org. Retrieved May 2, 2019.
  49. ^ Sigler, Chris. "416 Requested Range Not Satisfiable". GetStatusCode. Archived from the original on October 22, 2015. Retrieved October 16, 2015.
  50. ^ "RFC2616 on status 416". Tools.ietf.org. Retrieved November 11, 2015.
  51. ^ TheDeadLike. "HTTP/1.1 Status Codes 400 and 417, cannot choose which". serverFault. Retrieved October 16, 2015.
  52. ^ Larry Masinter (April 1, 1998). Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0). doi:10.17487/RFC2324. RFC 2324.
  53. ^ Barry Schwartz (August 26, 2014). "New Google Easter Egg For SEO Geeks: Server Status 418, I'm A Teapot". Search Engine Land.
  54. ^ Google's Teapot
  55. ^ "Hypertext Transfer Protocol version 2". March 2015. Retrieved April 25, 2015.
  56. ^ "9.1.1. Connection Reuse". RFC7540. May 2015.
  57. ^ Khare, R; Lawrence, S. "Upgrading to TLS Within HTTP/1.1". IETF. Network Working Group. Retrieved October 16, 2015.
  58. ^ Jump up to: a b c d Nottingham, M.; Fielding, R. (April 2012). "RFC 6585 – Additional HTTP Status Codes". Request for Comments. Internet Engineering Task Force. Retrieved May 1, 2012.
  59. ^ Bray, T. (February 2016). "An HTTP Status Code to Report Legal Obstacles". ietf.org. Retrieved March 7, 2015.
  60. ^ "Server Error Codes". CSGNetwork.com. Retrieved October 16, 2015.
  61. ^ mrGott. "HTTP Status Codes To Handle Errors In Your API". mrGott. Archived from the original on September 30, 2015. Retrieved October 16, 2015.
  62. ^ Fisher, Tim. "500 Internal Server Error". Lifewire. Retrieved February 22, 2017.
  63. ^ "HTTP Error 501 Not implemented". Check Up Down. Retrieved February 22, 2017.
  64. ^ Fisher, Tim. "502 Bad Gateway". Lifewire. Retrieved February 22, 2017.
  65. ^ alex. "What is the correct HTTP status code to send when a site is down for maintenance?". Stack Overflow. Retrieved October 16, 2015.
  66. ^ "HTTP Error 504 Gateway timeout". Check Up Down. Retrieved October 16, 2015.
  67. ^ "HTTP Error 505 - HTTP version not supported". Check Up Down. Retrieved October 16, 2015.
  68. ^ Holtman, Koen; Mutz, Andrew H. (March 1998). Transparent Content Negotiation in HTTP. IETF. doi:10.17487/RFC2295. RFC 2295. Retrieved October 24, 2009.
  69. ^ Nielsen, Henrik Frystyk; Leach, Paul; Lawrence, Scott (February 2000). An HTTP Extension Framework. IETF. doi:10.17487/RFC2774. RFC 2774. Retrieved October 24, 2009.
  70. ^ "ResumableHttpRequestsProposal". Archived from the original on October 13, 2015. Retrieved March 8, 2017.
  71. ^ "Apache ProxyErrorOverride". Retrieved June 7, 2018.
  72. ^ "Enum HttpStatus". Spring Framework. org.springframework.http. Retrieved October 16, 2015.
  73. ^ "Twitter Error Codes & Responses". Twitter. 2014. Retrieved January 20, 2014.
  74. ^ "Screenshot of error page" (bmp). Retrieved October 11, 2009.
  75. ^ Jump up to: a b "Using token-based authentication". ArcGIS Server SOAP SDK.
  76. ^ "HTTP Error Codes and Quick Fixes". Docs.cpanel.net. Retrieved October 15, 2015.
  77. ^ "Platform Considerations | Pantheon Docs". pantheon.io.
  78. ^ http://www.injosoft.se, Injosoft AB. "HTTP status codes - ascii-code.com". www.ascii-code.com. Retrieved December 23, 2016.
  79. ^
    "Error message when you try to log on to Exchange 2007 by using Outlook Web Access: "440 Login Time-out"". Microsoft. 2010. Retrieved November 13, 2013.
  80. ^ "2.2.6 449 Retry With Status Code". Microsoft. 2009. Retrieved October 26, 2009.
  81. ^ "MS-ASCMD, Section 3.1.5.2.2". Msdn.microsoft.com. Retrieved January 8, 2015.
  82. ^ "Ms-oxdisco". Msdn.microsoft.com. Retrieved January 8, 2015.
  83. ^ "ngx_http_request.h". nginx 1.9.5 source code. nginx inc. Retrieved January 9, 2016.
  84. ^ "ngx_http_special_response.c". nginx 1.9.5 source code. nginx inc. Retrieved January 9, 2016.
  85. ^ "return" directive (http_rewrite module) documentation.
  86. ^ "Troubleshooting: Error Pages". Cloudflare. Retrieved January 9, 2016.
  87. ^ "Railgun Listener to Origin Error". Cloudflare. Retrieved October 12, 2016.
  88. ^ "Error 1016 - Origin DNS error". Cloudflare.
at