Skip to content Skip to sidebar Skip to footer
Home / Nginx This Website Is Temporarily Unavailable Please Try Again Later

Nginx This Website Is Temporarily Unavailable Please Try Again Later

Post a Comment

Response codes of the Hypertext Transfer Protocol

This is a list of Hypertext Transfer Protocol (HTTP) response condition codes. Status codes are issued by a server in response to a client'due south asking made to the server. It includes codes from IETF Request for Comments (RFCs), other specifications, and some boosted codes used in some common applications of the HTTP. The kickoff digit of the status code specifies 1 of five standard classes of responses. The bulletin phrases shown are typical, merely whatsoever human-readable alternative may be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).[1]

The Cyberspace Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[2]

All HTTP response status codes are separated into five classes or categories. The first digit of the status code defines the class of response, while the final two digits do not have whatever classifying or categorization role. There are five classes divers by the standard:

  • 1xx informational response – the asking was received, standing procedure
  • 2xx successful – the request was successfully received, understood, and accepted
  • 3xx redirection – further action needs to be taken in gild to complete the asking
  • 4xx client error – the request contains bad syntax or cannot be fulfilled
  • 5xx server error – the server failed to fulfil an patently valid request

1xx informational response

An advisory response indicates that the request was received and understood. It is issued on a conditional basis while request processing continues. Information technology alerts the client to wait for a final response. The message consists only of the status line and optional header fields, and is terminated by an empty line. As the HTTP/ane.0 standard did not define any 1xx status codes, servers must non [annotation 1] ship a 1xx response to an HTTP/ane.0 compliant client except under experimental weather condition.[iii]

100 Proceed
The server has received the asking headers and the customer should go on to send the request body (in the case of a request for which a trunk needs to be sent; for example, a POST asking). Sending a large asking body to a server subsequently a request has been rejected for inappropriate headers would be inefficient. To accept a server check the request'south headers, a client must send Wait: 100-go along equally a header in its initial request and receive a 100 Continue status lawmaking in response before sending the body. If the client receives an error code such as 403 (Forbidden) or 405 (Method Not Allowed) and then information technology should not send the request's body. The response 417 Expectation Failed indicates that the request should be repeated without the Expect header as it indicates that the server does non back up expectations (this is the instance, for example, of HTTP/1.0 servers).[4]
101 Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to practise so.[5]
102 Processing (WebDAV; RFC 2518)
A WebDAV asking may contain many sub-requests involving file operations, requiring a long time to consummate the request. This code indicates that the server has received and is processing the request, but no response is available notwithstanding.[6] This prevents the client from timing out and bold the request was lost.
103 Early Hints (RFC 8297)
Used to render some response headers before final HTTP bulletin.[7]

2xx success

This class of status codes indicates the activeness requested past the customer was received, understood, and accepted.[2]

200 OK
Standard response for successful HTTP requests. The bodily response will depend on the asking method used. In a Get request, the response volition comprise an entity corresponding to the requested resources. In a POST asking, the response volition comprise an entity describing or containing the result of the activity.[eight]
201 Created
The asking has been fulfilled, resulting in the creation of a new resources.[9]
202 Accustomed
The request has been accepted for processing, but the processing has not been completed. The request might or might not be eventually acted upon, and may exist disallowed when processing occurs.[10]
203 Not-Authoritative Information (since HTTP/1.1)
The server is a transforming proxy (e.1000. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin'due south response.[11] [12]
204 No Content
The server successfully processed the request, and is not returning whatsoever content.[thirteen]
205 Reset Content
The server successfully candy the request, asks that the requester reset its document view, and is not returning any content.[14]
206 Fractional Content (RFC 7233)
The server is delivering only function of the resource (byte serving) due to a range header sent by the customer. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.[15]
207 Multi-Condition (WebDAV; RFC 4918)
The message body that follows is by default an XML message and can contain a number of separate response codes, depending on how many sub-requests were fabricated.[16]
208 Already Reported (WebDAV; RFC 5842)
The members of a DAV binding accept already been enumerated in a preceding part of the (multistatus) response, and are non being included again.
226 IM Used (RFC 3229)
The server has fulfilled a request for the resource, and the response is a representation of the result of ane or more case-manipulations practical to the current example.[17]

3xx redirection

This course of condition code indicates the client must take additional action to complete the request. Many of these condition codes are used in URL redirection.[two]

A user agent may carry out the additional action with no user interaction only if the method used in the 2d request is Go or HEAD. A user agent may automatically redirect a asking. A user amanuensis should notice and intervene to prevent cyclical redirects.[18]

300 Multiple Choices
Indicates multiple options for the resource from which the client may cull (via agent-driven content negotiation). For example, this code could exist used to present multiple video format options, to listing files with unlike filename extensions, or to suggest word-sense disambiguation.[19]
301 Moved Permanently
This and all futurity requests should be directed to the given URI. [20]
302 Found (Previously "Moved temporarily")
Tells the customer to look at (scan to) another URL. The HTTP/1.0 specification (RFC 1945) required the client to perform a temporary redirect with the aforementioned method (the original describing phrase was "Moved Temporarily"),[21] only popular browsers implemented 302 redirects past irresolute the method to Get. Therefore, HTTP/1.i added status codes 303 and 307 to distinguish between the two behaviours.[22]
303 See Other (since HTTP/1.1)
The response to the request can exist institute under some other URI using the GET method. When received in response to a POST (or PUT/DELETE), the client should presume that the server has received the information and should issue a new GET request to the given URI.[23]
304 Not Modified (RFC 7232)
Indicates that the resource has not been modified since the version specified by the request headers If-Modified-Since or If-None-Match. In such example, at that place is no need to retransmit the resources since the client still has a previously-downloaded copy.[24]
305 Utilise Proxy (since HTTP/ane.1)
The requested resource is available merely through a proxy, the address for which is provided in the response. For security reasons, many HTTP clients (such as Mozilla Firefox and Internet Explorer) practice not obey this status code.
306 Switch Proxy
No longer used. Originally meant "Subsequent requests should use the specified proxy."[26]
307 Temporary Redirect (since HTTP/ane.1)
In this case, the asking should be repeated with another URI; nevertheless, futurity requests should still use the original URI. In contrast to how 302 was historically implemented, the asking method is not allowed to exist inverse when reissuing the original request. For example, a POST request should exist repeated using some other Postal service request.[27]
308 Permanent Redirect (RFC 7538)
This and all futurity requests should be directed to the given URI. 308 parallel the behaviour of 301, but does not permit the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may go on smoothly.[28]

4xx client errors

A The Wikimedia 404 message

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

400 Bad Request
The server cannot or will not procedure the request due to an apparent client error (east.1000., malformed request syntax, size too large, invalid request bulletin framing, or deceptive request routing).[xxx]
401 Unauthorized (RFC 7235)
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not however been provided. The response must include a Www-Authenticate header field containing a claiming applicable to the requested resources. Encounter Basic access authentication and Assimilate access authentication.[31] 401 semantically means "unauthorised",[32] the user does non have valid authentication credentials for the target resource.
Notation: Some sites incorrectly upshot 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.[ citation needed ]
402 Payment Required
Reserved for future use. The original intention was that this code might be used as office of some form of digital cash or micropayment scheme, equally proposed, for example, past GNU Taler,[33] simply that has non yet happened, and this code is not widely used. Google Developers API uses this status if a particular developer has exceeded the daily limit on requests.[34] Sipgate uses this lawmaking if an account does not have sufficient funds to start a call.[35] Shopify uses this code when the store has not paid their fees and is temporarily disabled.[36] Stripe uses this code for failed payments where parameters were correct, for case blocked fraudulent payments.[37]
403 Forbidden
The asking independent valid information and was understood by the server, but the server is refusing activity. This may be due to the user not having the necessary permissions for a resources or needing an account of some sort, or attempting a prohibited action (eastward.thousand. creating a duplicate record where merely one is allowed). This code is also typically used if the request provided hallmark by answering the WWW-Authenticate header field challenge, but the server did not have that authentication. The request should non exist repeated.
404 Not Found
The requested resources could non be establish but may be available in the future. Subsequent requests by the client are permissible.
405 Method Non Allowed
A asking method is not supported for the requested resource; for example, a GET request on a class that requires information to be presented via POST, or a PUT asking on a read-just resources.
406 Not Acceptable
The requested resource is capable of generating simply content non acceptable according to the Accept headers sent in the request.[38] Run into Content negotiation.
407 Proxy Authentication Required (RFC 7235)
The client must showtime authenticate itself with the proxy.[39]
408 Request Timeout
The server timed out waiting for the asking. According to HTTP specifications: "The customer did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at whatever later fourth dimension."[40]
409 Conflict
Indicates that the request could not be candy considering of disharmonize in the current country of the resource, such as an edit conflict between multiple simultaneous updates.
410 Gone
Indicates that the resource requested is no longer bachelor and will not exist bachelor again. This should be used when a resources 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 resources from their indices.[41] Almost employ cases practise not require clients and search engines to purge the resources, and a "404 Not Constitute" may be used instead.
411 Length Required
The request did not specify the length of its content, which is required by the requested resource.[42]
412 Precondition Failed (RFC 7232)
The server does not meet ane of the preconditions that the requester put on the request header fields.[43]
413 Payload Likewise Large (RFC 7231)
The request is larger than the server is willing or able to procedure. Previously called "Request Entity Too Large".[44]
414 URI Too Long (RFC 7231)
The URI provided was too long for the server to process. Often the upshot of too much data existence encoded as a query-string of a GET request, in which example it should exist converted to a POST request.[45] Chosen "Asking-URI Too Long" previously.[46]
415 Unsupported Media Type (RFC 7231)
The request entity has a media type which the server or resource does non support. For example, the customer uploads an image as epitome/svg+xml, but the server requires that images utilize a unlike format.[47]
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.[48] Chosen "Requested Range Not Satisfiable" previously.[49]
417 Expectation Failed
The server cannot run into the requirements of the Look request-header field.[fifty]
418 I'thou a teapot (RFC 2324, RFC 7168)
This lawmaking was divers in 1998 as one of the traditional IETF Apr Fools' jokes, in RFC 2324, Hyper Text Coffee Pot Control Protocol, and is non expected to be implemented by actual HTTP servers. The RFC specifies this code should be returned by teapots requested to brew coffee.[51] This HTTP status is used every bit an Easter egg in some websites, such every bit Google.com'due south "I'1000 a teapot" easter egg.[52] [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 connexion reuse).[56]
422 Unprocessable Entity (WebDAV; RFC 4918)
The asking was well-formed only was unable to exist followed due to semantic errors.[16]
423 Locked (WebDAV; RFC 4918)
The resource that is being accessed is locked.[sixteen]
424 Failed Dependency (WebDAV; RFC 4918)
The request failed because it depended on some other request and that request failed (e.k., a PROPPATCH).[xvi]
425 Likewise Early (RFC 8470)
Indicates that the server is unwilling to risk processing a asking that might be replayed.
426 Upgrade Required
The client should switch to a different protocol such equally TLS/1.3, given in the Upgrade header field.[57]
428 Precondition Required (RFC 6585)
The origin server requires the request to be conditional. Intended to forbid the 'lost update' problem, where a client GETs a resource's land, modifies it, and PUTs it back to the server, when meanwhile a third political party has modified the state on the server, leading to a conflict.[58]
429 As well Many Requests (RFC 6585)
The user has sent too many requests in a given corporeality of time. Intended for utilise with charge per unit-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 admission to a resource or to a gear up of resource that includes the requested resource.[59] The code 451 was chosen as a reference to the novel Fahrenheit 451 (meet the Acknowledgements in the RFC).

5xx server errors

The server failed to fulfil a request.[sixty]

Response status codes beginning with the digit "v" betoken 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 asking, the server should include an entity containing an caption of the error situation, and indicate whether it is a temporary or permanent condition. Likewise, user agents should display whatever included entity to the user. These response codes are applicable to any request method.[61]

500 Internal Server Error
A generic fault 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 asking. Usually this implies future availability (e.g., a new feature of a web-service API).[63]
502 Bad Gateway
The server was acting equally a gateway or proxy and received an invalid response from the upstream server.[64]
503 Service Unavailable
The server cannot handle the request (considering it is overloaded or down for maintenance). Generally, this is a temporary state.[65]
504 Gateway Timeout
The server was acting equally 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 round reference.[68]
507 Insufficient Storage (WebDAV; RFC 4918)
The server is unable to shop the representation needed to complete the request.[16]
508 Loop Detected (WebDAV; RFC 5842)
The server detected an space 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 command access to the network (due east.1000., "captive portals" used to require agreement to Terms of Service before granting full Internet admission via a Wi-Fi hotspot).[58]

Unofficial codes

The post-obit codes are not specified by any standard.

419 Page Expired (Laravel Framework)
Used past the Laravel Framework when a CSRF Token is missing or expired.
420 Method Failure (Spring Framework)
A deprecated response used by the Leap Framework when a method has failed.[70]
420 Enhance Your Calm (Twitter)
Returned by version 1 of the Twitter Search and Trends API when the client is being rate express; versions i.one and later employ the 429 Too Many Requests response code instead.[71] The phrase "Heighten your calm" comes from the 1993 movie Sabotage Man, and its association with this number is probable a reference to cannabis.[ citation needed ]
430 Request Header Fields As well Large (Shopify)
Used by Shopify, instead of the 429 Also Many Requests response code, when too many URLs are requested inside a certain time frame.[72]
450 Blocked by Windows Parental Controls (Microsoft)
The Microsoft extension code indicated when Windows Parental Controls are turned on and are blocking access to the requested webpage.[73]
498 Invalid Token (Esri)
Returned by ArcGIS for Server. Lawmaking 498 indicates an expired or otherwise invalid token.[74]
499 Token Required (Esri)
Returned past ArcGIS for Server. Lawmaking 499 indicates that a token is required but was not submitted.[74]
509 Bandwidth Limit Exceeded (Apache Web Server/cPanel)
The server has exceeded the bandwidth specified by the server ambassador; this is often used by shared hosting providers to limit the bandwidth of customers.[75]
529 Site is overloaded
Used by Qualys in the SSLLabs server testing API to indicate that the site tin can't process the asking.[76]
530 Site is frozen
Used by the Pantheon web platform to indicate a site that has been frozen due to inactivity.[77]
598 (Informal convention) Network read timeout error
Used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.[78]
599 Network Connect Timeout Error
An mistake used by some HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.[79]

Internet Information Services

Microsoft'south Internet Information Services (IIS) spider web server expands the 4xx error infinite to signal errors with the client'south request.

440 Login Time-out
The customer's session has expired and must log in again.[80]
449 Retry With
The server cannot award the request because the user has not provided the required information.[81]
451 Redirect
Used in Exchange ActiveSync when either a more efficient server is bachelor or the server cannot access the users' mailbox.[82] The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server.[83]

IIS sometimes uses additional decimal sub-codes for more specific data,[84] however these sub-codes just appear in the response payload and in documentation, non in the place of an actual HTTP condition code.

nginx

The nginx web server software expands the 4xx error infinite to signal issues with the client's request.[85] [86]

444 No Response
Used internally[87] to instruct the server to render no data to the client and close the connection immediately.
494 Request header too large
Client sent too large request or likewise long header line.
495 SSL Certificate Fault
An expansion of the 400 Bad Request response code, used when the client has provided an invalid client document.
496 SSL Certificate Required
An expansion of the 400 Bad Request response lawmaking, used when a client certificate is required but not provided.
497 HTTP Asking Sent to HTTPS Port
An expansion of the 400 Bad Request response code, used when the client has made a HTTP asking to a port listening for HTTPS requests.
499 Client Closed Request
Used when the client has airtight the request before the server could send a response.

Cloudflare

Cloudflare'south opposite proxy service expands the 5xx series of errors space to point issues with the origin server.[88]

520 Web Server Returned an Unknown Error
The origin server returned an empty, unknown, or unexpected response to Cloudflare.[89]
521 Web Server Is Downward
The origin server refused connections from Cloudflare. Security solutions at the origin may be blocking legitimate connections from certain Cloudflare IP addresses.
522 Connexion Timed Out
Cloudflare timed out contacting the origin server.
523 Origin Is Unreachable
Cloudflare could not reach the origin server; for example, if the DNS records for the origin server are incorrect or missing.
524 A Timeout Occurred
Cloudflare was able to complete a TCP connection to the origin server, only did non receive a timely HTTP response.
525 SSL Handshake Failed
Cloudflare could not negotiate a SSL/TLS handshake with the origin server.
526 Invalid SSL Document
Cloudflare could not validate the SSL certificate on the origin web server. Too used by Cloud Foundry's gorouter.
527 Railgun Error
Fault 527 indicates an interrupted connexion betwixt Cloudflare and the origin server's Railgun server.[90]
530
Error 530 is returned along with a 1xxx fault.[91]

AWS Rubberband Load Balancer

Amazon's Elastic Load Balancing adds a few custom render codes

460
Client airtight the connection with the load balancer before the idle timeout period elapsed. Typically when client timeout is sooner than the Elastic Load Balancer'south timeout.[92]
463
The load balancer received an X-Forwarded-For request header with more than 30 IP addresses.[92]
561 Unauthorized
An error around authentication returned past a server registered with a load balancer. You configured a listener rule to authenticate users, but the identity provider (IdP) returned an error code when authenticating the user.[93]

Caching warning codes

The post-obit caching related warning codes are specified under RFC 7234. Unlike the other condition codes above, these are non sent as the response status in the HTTP protocol, merely as office of the "Alarm" HTTP header.[94] [95] Since this header is frequently neither sent by servers nor acknowledged by clients, information technology will soon be obsoleted by the HTTP Working Group.[96]

110 Response is Dried
The response provided by a cache is dried (the content's historic period exceeds a maximum age set by a Enshroud-Control header or heuristically called lifetime).
111 Revalidation Failed
The enshroud was unable to validate the response, due to an inability to reach the origin server.
112 Disconnected Performance
The cache is intentionally disconnected from the remainder of the network.
113 Heuristic Expiration
The cache heuristically chose a freshness lifetime greater than 24 hours and the response'due south age is greater than 24 hours.
199 Miscellaneous Warning
Capricious, not-specific warning. The warning text may be logged or presented to the user.
214 Transformation Applied
Added by a proxy if information technology applies any transformation to the representation, such equally changing the content encoding, media type or the similar.
299 Miscellaneous Persistent Warning
Aforementioned equally 199, but indicating a persistent warning.

Meet also

  • Custom error pages
  • List of FTP server return codes
  • Listing of HTTP header fields
  • Listing of SMTP server return codes
  • Common Log Format

Notes

  1. ^ Emphasised words and phrases such as must and should correspond estimation guidelines every bit given past RFC 2119

References

  1. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content". IETF. Archived from the original on May 25, 2017. Retrieved December xvi, 2017.
  2. ^ a b c "Hypertext Transfer Protocol (HTTP) Status Code Registry". Iana.org. Archived from the original on December xi, 2011. Retrieved January 8, 2015.
  3. ^ "10 Status Code Definitions". W3. Archived from the original on March sixteen, 2010. Retrieved October 16, 2015.
  4. ^ "Hypertext Transfer Protocol (HTTP/one.i): Semantics and Content – 5.i.1. Expect". Archived from the original on May 25, 2017. Retrieved September 27, 2017.
  5. ^ "101". httpstatus. Archived from the original on October 30, 2015. Retrieved October 16, 2015.
  6. ^ Goland, Yaronn; Whitehead, Jim; Faizi, Asad; Carter, Steve R.; Jensen, Del (Feb 1999). HTTP Extensions for Distributed Authoring – WEBDAV. IETF. doi:x.17487/RFC2518. RFC 2518. Retrieved Oct 24, 2009.
  7. ^ Oku, Kazuho (Dec 2017). An HTTP Status Code for Indicating Hints. IETF. doi:10.17487/RFC8297. RFC 8297. Retrieved December 20, 2017.
  8. ^ "200 OK". Hypertext Transfer Protocol – HTTP/1.1. IETF. June 1999. sec. 10.two.one. doi:ten.17487/RFC2616. RFC 2616. Retrieved August 30, 2016.
  9. ^ Stewart, Marker; djna. "Create request with POST, which response codes 200 or 201 and content". Stack Overflow. Archived from the original on Oct 11, 2016. Retrieved Oct 16, 2015.
  10. ^ "202 Accepted". httpstatuses.com . Retrieved Feb 23, 2022.
  11. ^ "RFC 7231, Section 6.three.iv". Archived from the original on May 25, 2017.
  12. ^ "RFC 7230, Section 5.7.2". Archived from the original on February 3, 2016. Retrieved February 3, 2016.
  13. ^ Simmance, Chris. "Server Response Codes And What They Mean". koozai. Archived from the original on September 26, 2015. Retrieved October 16, 2015.
  14. ^ "IETF RFC7231 section 6.iii.six. – 205 Reset Content". IETF.org. Archived from the original on May 25, 2017. Retrieved September 6, 2018.
  15. ^ "diff --git a/linkchecker.module b/linkchecker.module". Drupal. Archived from the original on March iv, 2016. Retrieved October 16, 2015.
  16. ^ 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.
  17. ^ Delta encoding in HTTP. IETF. January 2002. doi:ten.17487/RFC3229. RFC 3229. Retrieved February 25, 2011.
  18. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content". IETF. Archived from the original on May 25, 2017. Retrieved February 13, 2016.
  19. ^ "300". httpstatus. Archived from the original on October 17, 2015. Retrieved October xvi, 2015.
  20. ^ "301". httpstatus. Archived from the original on Oct 27, 2015. Retrieved October xvi, 2015.
  21. ^ Berners-Lee, Tim; Fielding, Roy T.; Nielsen, Henrik Frystyk (May 1996). Hypertext Transfer Protocol – HTTP/ane.0. IETF. doi:x.17487/RFC1945. RFC 1945. Retrieved Oct 24, 2009.
  22. ^ "Hypertext Transfer Protocol (HTTP/1.ane): Semantics and Content, Section half dozen.iv". IETF. Archived from the original on May 25, 2017. Retrieved June 12, 2014.
  23. ^ "303". httpstatus. Archived from the original on October 22, 2015. Retrieved October 16, 2015.
  24. ^ "304 Not Modified". Mozilla Developer Network. Archived from the original on July two, 2017. Retrieved July 6, 2017.
  25. ^ Cohen, Josh. "HTTP/1.1 305 and 306 Response Codes". HTTP Working Group. Archived from the original on September 8, 2014. Retrieved September 8, 2014.
  26. ^ "Hypertext Transfer Protocol (HTTP/ane.1): Semantics and Content, Section vi.4.7 307 Temporary Redirect". IETF. 2014. Archived from the original on May 25, 2017. Retrieved September 20, 2014.
  27. ^ "The Hypertext Transfer Protocol Status Lawmaking 308 (Permanent Redirect)". Internet Engineering science Task Force. April 2015. Archived from the original on Apr xvi, 2015. Retrieved April six, 2015.
  28. ^ "East Explanation of Failure Codes". Oracle. Archived from the original on February xvi, 2015. Retrieved October 16, 2015.
  29. ^ "RFC7231 on code 400". Tools.ietf.org. Archived from the original on May 25, 2017. Retrieved January eight, 2015.
  30. ^ "401". httpstatus. Archived from the original on October 17, 2015. Retrieved Oct 16, 2015.
  31. ^ "RFC7235 on lawmaking 401". Tools.ietf.org. Archived from the original on Feb 7, 2015. Retrieved February eight, 2015.
  32. ^ "The GNU Taler tutorial for PHP Spider web shop developers 0.four.0". docs.taler.internet. Archived from the original on November viii, 2017. Retrieved October 29, 2017.
  33. ^ "Google API Standard Mistake Responses". 2016. Archived from the original on May 25, 2017. Retrieved June 21, 2017.
  34. ^ "Sipgate API Documentation". Archived from the original on July 10, 2018. Retrieved July 10, 2018.
  35. ^ "Shopify Documentation". Archived from the original on July 25, 2018. Retrieved July 25, 2018.
  36. ^ "Stripe API Reference – Errors". stripe.com . Retrieved Oct 28, 2019.
  37. ^ Singh, Prabhat; user1740567. "Jump 3.x JSON status 406 "characteristics non acceptable according to the asking "take" headers ()"". Stack Overflow. Archived from the original on October xi, 2016. Retrieved October 16, 2015.
  38. ^ "407". httpstatus. Archived from the original on October 11, 2015. Retrieved October 16, 2015.
  39. ^ "408". httpstatus. Archived from the original on Oct 31, 2015. Retrieved October 16, 2015.
  40. ^ "Does Google treat 404 and 410 status codes differently? (Youtube)". 2014. Archived from the original on January eight, 2015. Retrieved February iv, 2015.
  41. ^ "List of HTTP condition codes". Google Books . Retrieved October sixteen, 2015.
  42. ^ "RFC7232, section 4.two". Archived from the original on June 26, 2019. Retrieved June xx, 2019.
  43. ^ "RFC2616 on status 413". Tools.ietf.org. Archived from the original on March 7, 2011. Retrieved November xi, 2015.
  44. ^ user27828. "Become Asking – Why is my URI so long?". Stack Overflow. Archived from the original on October 11, 2016. Retrieved Oct 16, 2015.
  45. ^ "RFC2616 on status 414". Tools.ietf.org. Archived from the original on March vii, 2011. Retrieved November 11, 2015.
  46. ^ "RFC7231 on status 415". Tools.ietf.org. Archived from the original on May 25, 2017. Retrieved May 2, 2019.
  47. ^ Sigler, Chris. "416 Requested Range Not Satisfiable". GetStatusCode. Archived from the original on October 22, 2015. Retrieved October 16, 2015.
  48. ^ "RFC2616 on condition 416". Tools.ietf.org. Archived from the original on March 7, 2011. Retrieved Nov eleven, 2015.
  49. ^ TheDeadLike. "HTTP/i.ane Status Codes 400 and 417, cannot choose which". serverFault. Archived from the original on Oct ten, 2015. Retrieved October 16, 2015.
  50. ^ Larry Masinter (Apr 1, 1998). Hyper Text Coffee Pot Command Protocol (HTCPCP/1.0). doi:10.17487/RFC2324. RFC 2324. Any attempt to brew coffee with a teapot should result in the error code "418 I'grand a teapot". The resulting entity body MAY be short and stout.
  51. ^ I'1000 a teapot
  52. ^ Barry Schwartz (August 26, 2014). "New Google Easter Egg For SEO Geeks: Server Status 418, I'one thousand A Teapot". Search Engine Country. Archived from the original on November xv, 2015. Retrieved November iv, 2015.
  53. ^ "Google's Teapot". Retrieved Oct 23, 2017. [ dead link ]
  54. ^ "Hypertext Transfer Protocol version 2". March 2015. Archived from the original on April 25, 2015. Retrieved Apr 25, 2015.
  55. ^ "9.1.1. Connexion Reuse". RFC7540. May 2015. Archived from the original on June 23, 2015. Retrieved July 11, 2017.
  56. ^ Khare, R; Lawrence, S. "Upgrading to TLS Within HTTP/1.1". IETF. Network Working Group. Archived from the original on October 8, 2015. Retrieved October 16, 2015.
  57. ^ a b c d Nottingham, M.; Fielding, R. (Apr 2012). "RFC 6585 – Boosted HTTP Status Codes". Request for Comments. Net Engineering Task Force. Archived from the original on May 4, 2012. Retrieved May 1, 2012.
  58. ^ Bray, T. (Feb 2016). "An HTTP Status Lawmaking to Study Legal Obstacles". ietf.org. Archived from the original on March iv, 2016. Retrieved March seven, 2015.
  59. ^ "Server Error Codes". CSGNetwork.com. Archived from the original on October 8, 2015. Retrieved October 16, 2015.
  60. ^ mrGott. "HTTP Status Codes To Handle Errors In Your API". mrGott. Archived from the original on September 30, 2015. Retrieved October 16, 2015.
  61. ^ Fisher, Tim. "500 Internal Server Mistake". Lifewire. Archived from the original on February 23, 2017. Retrieved February 22, 2017.
  62. ^ "HTTP Fault 501 Non implemented". Check Upward Down. Archived from the original on May 12, 2017. Retrieved February 22, 2017.
  63. ^ Fisher, Tim. "502 Bad Gateway". Lifewire. Archived from the original on February 23, 2017. Retrieved Feb 22, 2017.
  64. ^ alex. "What is the right HTTP status lawmaking to send when a site is downwardly for maintenance?". Stack Overflow. Archived from the original on October xi, 2016. Retrieved October 16, 2015.
  65. ^ "HTTP Error 504 Gateway timeout". Bank check Upward Downwardly. Archived from the original on September 20, 2015. Retrieved October xvi, 2015.
  66. ^ "HTTP Error 505 – HTTP version not supported". Check Up Downwards. Archived from the original on September 24, 2015. Retrieved Oct sixteen, 2015.
  67. ^ Holtman, Koen; Mutz, Andrew H. (March 1998). Transparent Content Negotiation in HTTP. IETF. doi:10.17487/RFC2295. RFC 2295. Retrieved October 24, 2009.
  68. ^ Nielsen, Henrik Frystyk; Leach, Paul; Lawrence, Scott (February 2000). An HTTP Extension Framework. IETF. doi:10.17487/RFC2774. RFC 2774. Retrieved Oct 24, 2009.
  69. ^ "Enum HttpStatus". Spring Framework. org.springframework.http. Archived from the original on Oct 25, 2015. Retrieved October 16, 2015.
  70. ^ "Twitter Mistake Codes & Responses". Twitter. 2014. Archived from the original on September 27, 2017. Retrieved January 20, 2014.
  71. ^ "HTTP Status Codes and SEO: what you need to know". ContentKing . Retrieved August 9, 2019.
  72. ^ "Screenshot of error page". Archived from the original (bmp) on May 11, 2013. Retrieved October xi, 2009.
  73. ^ a b "Using token-based authentication". ArcGIS Server SOAP SDK. Archived from the original on September 26, 2014. Retrieved September 8, 2014.
  74. ^ "HTTP Error Codes and Quick Fixes". Docs.cpanel.net. Archived from the original on November 23, 2015. Retrieved Oct 15, 2015.
  75. ^ "SSL Labs API v3 Documentation". github.com.
  76. ^ "Platform Considerations | Pantheon Docs". pantheon.io. Archived from the original on January six, 2017. Retrieved Jan five, 2017.
  77. ^ http://www.injosoft.se, Injosoft AB. "HTTP status codes - ascii-code.com". www.ascii-code.com. Archived from the original on Jan 7, 2017. Retrieved December 23, 2016.
  78. ^ "599 Network Connect Timeout Error". httpstatuses.com . Retrieved November 17, 2021.
  79. ^ "Error message when y'all try to log on to Exchange 2007 by using Outlook Web Admission: "440 Login Time-out"". Microsoft. 2010. Retrieved Nov xiii, 2013.
  80. ^ "2.ii.6 449 Retry With Condition Code". Microsoft. 2009. Archived from the original on October 5, 2009. Retrieved October 26, 2009.
  81. ^ "MS-ASCMD, Department 3.1.5.2.2". Msdn.microsoft.com. Archived from the original on March 26, 2015. Retrieved Jan 8, 2015.
  82. ^ "Ms-oxdisco". Msdn.microsoft.com. Archived from the original on July 31, 2014. Retrieved Jan viii, 2015.
  83. ^ "The HTTP status codes in IIS 7.0". Microsoft. July 14, 2009. Archived from the original on April 9, 2009. Retrieved April 1, 2009.
  84. ^ "ngx_http_request.h". nginx one.9.5 source code. nginx inc. Archived from the original on September nineteen, 2017. Retrieved January nine, 2016.
  85. ^ "ngx_http_special_response.c". nginx 1.9.5 source lawmaking. nginx inc. Archived from the original on May 8, 2018. Retrieved January 9, 2016.
  86. ^ "return" directive Archived March i, 2018, at the Wayback Machine (http_rewrite module) documentation.
  87. ^ "Troubleshooting: Error Pages". Cloudflare. Archived from the original on March 4, 2016. Retrieved January 9, 2016.
  88. ^ "Error 520: web server returns an unknown error". Cloudflare. Retrieved November one, 2019.
  89. ^ "527 Error: Railgun Listener to origin error". Cloudflare. Archived from the original on Oct thirteen, 2016. Retrieved October 12, 2016.
  90. ^ "Fault 530". Cloudflare. Retrieved November 1, 2019.
  91. ^ a b "Troubleshoot Your Application Load Balancers – Elastic Load Balancing". docs.aws.amazon.com . Retrieved August 27, 2019.
  92. ^ "Troubleshoot your Application Load Balancers - Elastic Load Balancing". docs.aws.amazon.com . Retrieved January 24, 2021.
  93. ^ "Hypertext Transfer Protocol (HTTP/i.1): Caching". datatracker.ietf.org . Retrieved September 25, 2021.
  94. ^ "Warning - HTTP | MDN". programmer.mozilla.org . Retrieved August xv, 2021. CC BY-SA icon.svg Some text was copied from this source, which is bachelor under a Creative Commons Attribution-ShareAlike ii.5 Generic (CC BY-SA 2.5) license.
  95. ^ "HTTP Caching (typhoon-ietf-httpbis-cache-19), Section 5.v". datatracker.ietf.org . Retrieved September 25, 2021.

External links

  • RFC 7231 – Hypertext Transfer Protocol (HTTP/i.1): Semantics and Content – Department half-dozen, Response Status Codes
  • Hypertext Transfer Protocol (HTTP) Condition Code Registry
  • Microsoft Cognition Base: MSKB943891: The HTTP status codes in IIS vii.0
  • Microsoft Role Noesis Base: Error Code two–11

greshamroutionce.blogspot.com

Source: https://en.wikipedia.org/wiki/List_of_HTTP_status_codes

Post a Comment for "Nginx This Website Is Temporarily Unavailable Please Try Again Later"