List of HTTP status codes

From Wikipedia, the free encyclopedia
(Redirected from HTTP 304)

Template:Short description

  1. REDIRECT Template:Protection padlock

Template:Use American English Script error: No such module "Unsubst". Script error: No such module "Sidebar".

This article lists standard and notable non-standard HTTP response status codes. Standardized codes are defined by IETF as documented in Request for Comments (RFC) publications and maintained by the IANA.[1] Other, non-standard values are used by various servers. The descriptive text after the numeric code

  1. REDIRECT Template:En dash

Template:R protected the reason phrase

  1. REDIRECT Template:En dash

Template:R protected is shown here with typical value, but in practice, can be different or omitted.

Standard codes

Status codes defined by IETF are listed below. Emphasized terms must, must not and should are interpretation guidelines as given by Template:IETF RFC.

1xx informational response

An informational response indicates that the request was received and understood and is being processed. It alerts the client to wait for a final response. The message does not contain a body. As the HTTP/1.0 standard did not define any 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 compliant client except under experimental conditions.

Script error: No such module "anchor".100 Continue
The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent, such as a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. If the client receives an error code such as 403 (Forbidden) or 405 (Method Not Allowed) then it 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 not support expectations (this is the case, for example, of HTTP/1.0 servers).Template:Ref RFC
Script error: No such module "anchor".101 Switching Protocols
The requester has asked the server to switch protocols and the server has agreed to do so.
Script error: No such module "anchor".102 Processing (WebDAV; RFC 2518)
A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. This code indicates that the server has received and is processing the request, but no response is available yet.Template:Ref RFC This prevents the client from timing out and assuming the request was lost. The status code is deprecated.[2]
Script error: No such module "anchor".103 Early Hints (RFC 8297)
Used to return some response headers before final HTTP message.Template:Ref RFC

2xx success

A success status indicates that the action requested by the client was received, understood, and accepted.[1]

Script error: No such module "anchor".200 OK
Standard response for successful HTTP requests. The actual response will depend on the request method used. In a GET request, the response will contain an entity corresponding to the requested resource. In a POST request, the response will contain an entity describing or containing the result of the action.
Script error: No such module "anchor".201 Created
The request has been fulfilled, resulting in the creation of a new resource.[3]
Script error: No such module "anchor".202 Accepted
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 be disallowed when processing occurs.
Script error: No such module "anchor".203 Non-Authoritative Information (since HTTP/1.1)
The server is a transforming proxy (e.g. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response.Template:Ref RFCTemplate:Ref RFC
Script error: No such module "anchor".204 No Content
The server successfully processed the request, and is not returning any content.
Script error: No such module "anchor".205 Reset Content
The server successfully processed the request, asks that the requester reset its document view, and is not returning any content.
Script error: No such module "anchor".206 Partial Content
The server is delivering only part of the resource (byte serving) due to a range header sent by the client. The range header is used by HTTP clients to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.
Script error: No such module "anchor".207 Multi-Status (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 made.Template:Ref RFC
Script error: No such module "anchor".208 Already Reported (WebDAV; RFC 5842)
The members of a DAV binding have already been enumerated in a preceding part of the (multistatus) response, and are not being included again.
Script error: No such module "anchor".226 IM Used (RFC 3229)
The server has fulfilled a request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance.Template:Ref RFC

3xx redirection

A 3xx status indicates that the client must take additional action, generally URL redirection, to complete the request.[1] A user agent may carry out the additional action with no user interaction if the method used in the additional request is GET or HEAD. A user agent should prevent cyclical redirects.Template:Ref RFC

Script error: No such module "anchor".300 Multiple Choices
Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). For example, this code could be used to present multiple video format options, to list files with different filename extensions, or to suggest word-sense disambiguation.
Script error: No such module "anchor".301 Moved Permanently
The link target was moved such that the request and future similar requests should be redirected to the given URI. If a client has link-editing capabilities, it should update references to the request URL. The response is cacheable unless indicated otherwise. Except for a GET request, the body should contain a hyperlink to the new URL(s). Except for a GET or HEAD request, the client must ask the user before redirecting.[4]Template:PbThis code is considered best practice for upgrading users from HTTP to HTTPS. Both Bing and Google recommend using this code to change the URL of a page as it is shown in search engine results, providing that URL will permanently change and is not due to be changed again any time soon.[5][6]
Script error: No such module "anchor".302 Found
Indicates that the resource is accessible via an alternate URL indicated in the Location header field. The HTTP/1.0 specification (which used reason phrase "Moved Temporarily") required the client to redirect with the same method,Template:Ref RFC but popular browsers instead changed the request to GET.[7] For this reason, HTTP/1.1 (Template:IETF RFC) added two status codes: 303 which requires changing the request to a GET and 307 which preserves the original request type. Despite the greater clarity provided by this disambiguation, the 302 code is still used in web frameworks to preserve compatibility with browsers that do not support HTTP/1.1.[8]Template:Ref RFC As a consequence, Template:IETF RFC (the update of Template:IETF RFC) changes the definition to allow user agents to rewrite POST to GET.[9]
Script error: No such module "anchor".303 See Other (since HTTP/1.1)
If a server responds to a POST or other non-idempotent request with this code and a location header field, the client is expected to issue a GET request to the specified location. To trigger a request to the target resource using the same method, the server responds with 307 instead.
Use of this code has been proposed[10] as one way of responding to a request for a URI that identifies a real-world object according to Semantic Web theory (the other being the use of hash URIs).[11][10] For example, if http://www.example.com/id/aliceTemplate:Cbignore identifies a person, Alice, then it would be inappropriate for a server to respond to a GET request with 200 OK, as the server could not deliver Alice herself. Instead, the server would respond with 303 to redirect to a URI that provides a description of the person Alice.[10]
Sometimes, this code is used when providing an HTTP-based web API that needs to respond to the caller immediately, but continue executing asynchronously, such as a long-lived image conversion. The web API provides a status check URI that allows the client to check on the operation's status. When complete, the response may contain this status code and a redirect URI to the final result.[12]
Script error: No such module "anchor".304 Not Modified
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 case, there is no need to retransmit the resource since the client still has a previously-downloaded copy.
Script error: No such module "anchor".305 Use Proxy (since HTTP/1.1)
The requested resource is available only 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) do not obey this status code.[13]
Script error: No such module "anchor".306 Switch Proxy
No longer used. Originally meant "Subsequent requests should use the specified proxy."
Script error: No such module "anchor".307 Temporary Redirect (since HTTP/1.1)
In this case, the request should be repeated with another URI; however, future requests should still use the original URI. In contrast to how 302 was historically implemented, the request method is not allowed to be changed when reissuing the original request. For example, a POST request should be repeated using another POST request.
Script error: No such module "anchor".308 Permanent Redirect
This and all future requests should be directed to the given URI. 308 parallels the behavior of 301, but does not allow the HTTP method to change. So, for example, submitting a form to a permanently redirected resource may continue smoothly.

4xx client error

A The Wikimedia 404 message
404 error on Wikimedia

A 4xx status code is for situations in which an 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.

Script error: No such module "anchor".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).
Script error: No such module "anchor".401 Unauthorized
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. 401 semantically means "unauthenticated", the user does not have valid authentication credentials for the target resource.
Script error: No such module "anchor".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,[14] but that has not 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.[15] Sipgate uses this code if an account does not have sufficient funds to start a call.[16] Shopify uses this code when the store has not paid their fees and is temporarily disabled.[17] Stripe uses this code for failed payments where parameters were correct, for example blocked fraudulent payments.[18] Cloudflare Turnstile uses this code when requesting resources with cURL. x402 is an open standard that repurposes the HTTP 402 "Payment Required" status code.
Script error: No such module "anchor".403 Forbidden
Script error: No such module "Labelled list hatnote".
The request was valid, but the server refuses action. This may be due to the user not having permission to a resource or needing an account of some sort, or attempting a prohibited action (e.g. creating a duplicate record where only one is allowed). This code is also typically used if the request provided authentication by answering the WWW-Authenticate header field challenge, but the server did not accept that authentication. The request should not be repeated.
This code differs from 401 in that while 401 is returned when the client has not authenticated, and implies that a successful response may be returned following valid authentication, 403 is returned when the client is not permitted access to the resource despite providing authentication such as insufficient permissions of the authenticated account.
The Apache web server returns 403 in response to a request for URL[19] paths that corresponded to a file system directory when directory listing is disabled and there is no Directory Index directive to specify an existing file to be returned to the browser. Some administrators configure the Mod proxy extension to block such requests and this will also return 403. IIS responds in the same way when directory listings are denied in that server. In WebDAV, 403 is returned if the client issued a PROPFIND request but did not also issue the required Depth header or issued a Depth header of infinity.[19]
Script error: No such module "anchor".404 Not Found
Script error: No such module "Labelled list hatnote".
The requested resource could not be found but may be available in the future. Subsequent requests by the client are permissible.
Script error: No such module "anchor".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).
Script error: No such module "anchor".406 Not Acceptable
The requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request. See Content negotiation.
Script error: No such module "anchor".407 Proxy Authentication Required
The client must first authenticate itself with the proxy.
Script error: No such module "anchor".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."
Script error: No such module "anchor".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.[20]
Script error: No such module "anchor".410 Gone
Indicates that the resource requested was previously in use but 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. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.
Script error: No such module "anchor".411 Length Required
The request did not specify the length of its content, which is required by the requested resource.
Script error: No such module "anchor".412 Precondition Failed
The server does not meet one of the preconditions that the requester put on the request header fields.
Script error: No such module "anchor".413 Content Too Large
The request is larger than the server is willing or able to process. Previously called "Request Entity Too Large" and "Payload Too Large".Template:Ref RFCTemplate:Ref RFC
Script error: No such module "anchor".414 URI Too Long
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. Called "Request-URI Too Long" previously.Template:Ref RFC
Script error: No such module "anchor".415 Unsupported Media Type
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.
Script error: No such module "anchor".416 Range Not Satisfiable
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. Called "Requested Range Not Satisfiable" previously.Template:Ref RFC
Script error: No such module "anchor".417 Expectation Failed
The server cannot meet the requirements of the Expect request-header field.[21]
Script error: No such module "anchor".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.Template:Ref RFC This HTTP status is used as an Easter egg in some websites, such as Google.com's "I'm a teapot" easter egg.[22][23] Sometimes, this status code is also used as a response to a blocked request, instead of the more appropriate 403 Forbidden.[24][25]
Script error: No such module "anchor".421 Misdirected Request
The request was directed at a server that is not able to produce a response (for example because of connection reuse).
Script error: No such module "anchor".422 Unprocessable Content
The request was well-formed (i.e., syntactically correct) but could not be processed.Template:Ref RFC
Script error: No such module "anchor".423 Locked (WebDAV; RFC 4918)
The resource that is being accessed is locked.Template:Ref RFC
Script error: No such module "anchor".424 Failed Dependency (WebDAV; RFC 4918)
The request failed because it depended on another request and that request failed (e.g., a PROPPATCH).Template:Ref RFC
Script error: No such module "anchor".425 Too Early (RFC 8470)
Indicates that the server is unwilling to risk processing a request that might be replayed.
Script error: No such module "anchor".426 Upgrade Required
The client should switch to a different protocol such as TLS/1.3, given in the Upgrade header field.
Script error: No such module "anchor".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.Template:Ref RFC
Script error: No such module "anchor".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.[26]
Script error: No such module "anchor".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.[26]
Script error: No such module "anchor".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.[27] The code 451 was chosen as a reference to the novel Fahrenheit 451.[28] Script error: No such module "Labelled list hatnote".

5xx server error

5xx status indicates that 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.

Script error: No such module "anchor".500 Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
Script error: No such module "anchor".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).
Script error: No such module "anchor".502 Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
Script error: No such module "anchor".503 Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance). Generally, this is a temporary state.[29]
Script error: No such module "anchor".504 Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
Script error: No such module "anchor".505 HTTP Version Not Supported
The server does not support the HTTP version used in the request.
Script error: No such module "anchor".506 Variant Also Negotiates (RFC 2295)
Transparent content negotiation for the request results in a circular reference.Template:Ref RFC
Script error: No such module "anchor".507 Insufficient Storage (WebDAV; RFC 4918)
The server is unable to store the representation needed to complete the request.Template:Ref RFC
Script error: No such module "anchor".508 Loop Detected (WebDAV; RFC 5842)
The server detected an infinite loop while processing the request (sent instead of 208 Already Reported).
Script error: No such module "anchor".510 Not Extended (RFC 2774)
Further extensions to the request are required for the server to fulfil it.Template:Ref RFC
Script error: No such module "anchor".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).[26]
Script error: No such module "anchor".

Nonstandard codes

The following codes are used by various web servers but not specified by an IETF standard.

Internet Information Services

Microsoft's Internet Information Services (IIS) web server expands the 4xx error space to signal errors with the client's request. IIS sometimes uses additional decimal sub-codes for more specific information,[30] however these sub-codes only appear in the response payload and in documentation, not in the place of an actual HTTP status code.

Script error: No such module "anchor". 440 Login Time-out
The client's session has expired and must log in again.[31]
Script error: No such module "anchor". 449 Retry With
The server cannot honor the request because the user has not provided the required information.[32]
Script error: No such module "anchor". 450 Blocked by Windows Parental Controls
Indicates that Windows Parental Controls block access to the requested webpage.[33]
Script error: No such module "anchor". 451 Redirect
Used in Exchange ActiveSync when either a more efficient server is available or the server cannot access the users' mailbox.[34] The client is expected to re-run the HTTP AutoDiscover operation to find a more appropriate server.[35]

nginx

The nginx web server software expands the 4xx error space to signal issues with the client's request.[36][37]

Script error: No such module "anchor". 444 No Response
Used internally[38] to instruct the server to return no information to the client and close the connection immediately.
Script error: No such module "anchor". 494 Request header too large
Client sent too large request or too long header line.
Script error: No such module "anchor". 495 SSL Certificate Error
An expansion of the 400 Bad Request response code, used when the client has provided an invalid client certificate.
Script error: No such module "anchor". 496 SSL Certificate Required
An expansion of the 400 Bad Request response code, used when a client certificate is required but not provided.
Script error: No such module "anchor". 497 HTTP Request Sent to HTTPS Port
An expansion of the 400 Bad Request response code, used when the client has made a HTTP request to a port listening for HTTPS requests.
Script error: No such module "anchor". 499 Client Closed Request
Used when the client has closed the request before the server could send a response.

Cloudflare

Cloudflare's reverse proxy service expands the 5xx series of errors space to signal issues with the origin server.[39]

Script error: No such module "anchor". 520 Web Server Returned an Unknown Error
The origin server returned an empty, unknown, or unexpected response to Cloudflare.[40]
Script error: No such module "anchor". 521 Web Server Is Down
The origin server refused connections from Cloudflare. Security solutions at the origin may be blocking legitimate connections from certain Cloudflare IP addresses.[41]
Script error: No such module "anchor". 522 Connection Timed Out
Cloudflare timed out contacting the origin server.[42]
Script error: No such module "anchor". 523 Origin Is Unreachable
Cloudflare could not contact the origin server.[43]
Script error: No such module "anchor". 524 A Timeout Occurred
Cloudflare was able to complete a TCP connection to the origin server, but the origin did not provide a timely HTTP response.[44]
Script error: No such module "anchor". 525 SSL Handshake Failed
Cloudflare could not negotiate a SSL/TLS handshake with the origin server.[45][46]
Script error: No such module "anchor". 526 Invalid SSL Certificate
Cloudflare could not validate the SSL certificate on the origin web server.[47][48] Also used by Cloud Foundry's gorouter.
Script error: No such module "anchor". 527 Railgun Error (obsolete)
Error 527 indicated an interrupted connection between Cloudflare and the origin server's Railgun server.[49] This error is obsolete as Cloudflare has deprecated Railgun.
Script error: No such module "anchor". 530 Origin Unavailable
Cloudflare was unable to resolve the origin hostname, preventing it from establishing a connection to the origin server. The body of the response contains an 1xxx error.[50][51]

AWS Elastic Load Balancing

Amazon Web Services' Elastic Load Balancing adds a few custom return codes to signal issues either with the client request or with the origin server.[52]

Script error: No such module "anchor". 000
Returned with an HTTP/2 GOAWAY frame if the compressed length of any of the headers exceeds 8K bytes or if more than 10K requests are served through one connection.[52]
Script error: No such module "anchor". 460
Client closed the connection with the load balancer before the idle timeout period elapsed. Typically, when client timeout is sooner than the Elastic Load Balancer's timeout.[52]
Script error: No such module "anchor". 463
The load balancer received an X-Forwarded-For request header with more than 30 IP addresses.[52]
Script error: No such module "anchor". 464
Incompatible protocol versions between Client and Origin server.[52]
Script error: No such module "anchor". 561 Unauthorized
An error around authentication returned by a server registered with a load balancer. A listener rule is configured to authenticate users, but the identity provider (IdP) returned an error code when authenticating the user.[52]

Apache

Used by Apache HTTP Server.

Script error: No such module "anchor". 509 Bandwidth Limit Exceeded
The server has exceeded the bandwidth specified by the server administrator; this is often used by shared hosting providers to limit the bandwidth of customers.[53] Also used by cPanel.

Laravel framework

Used by Laravel Framework.

Script error: No such module "anchor". 419 Page Expired
A CSRF Token is missing or expired.[54]

Spring Framework

Used by Spring Framework.

Script error: No such module "anchor". 420 Method Failure
A deprecated response status proposed during the development of WebDAV[55] used by the Spring Framework when a method has failed.[56]

Twitter

Used by Twitter.

420 Enhance Your Calm
Returned by version 1 of the Twitter Search and Trends API when the client is being rate limited; versions 1.1 and later use the 429 Too Many Requests response code instead.[57] The phrase "Enhance your calm" comes from the 1993 movie Demolition Man, and its association with this number is likely a reference to cannabis.Script error: No such module "Unsubst".

Shopify

Used by Shopify.

430 Request Header Fields Too Large
A deprecated response used by Shopify, instead of the 429 Too Many Requests response code, when too many URLs are requested within a certain time frame.[58]
430 Shopify Security Rejection
Used by Shopify to signal that the request was deemed malicious.[59]
530 Origin DNS Error
Indicates that Cloudflare can't resolve the requested DNS record.[59]
Script error: No such module "anchor". 540 Temporarily Disabled
Indicates that the requested endpoint has been temporarily disabled.[59]
Script error: No such module "anchor". 783 Unexpected Token
Indicates that the request includes a JSON syntax error.[59]

ArcGIS Server

Used by ArcGIS Server.

Script error: No such module "anchor". 498 Invalid Token
Indicates an expired or otherwise invalid token.[60]
Script error: No such module "anchor". 499 Token Required
Indicates that a token is required but was not submitted.[60]

cPanel

Used by cPanel.

Script error: No such module "anchor". 508 Resource Limit Is Reached
Used instead of 503 when the server's account has exceeded the resources assigned to it, such as CPU/RAM usage or number of concurrent processes.[61]

SSLLabs server testing API

Used by Qualys in the SSLLabs server testing API.

Script error: No such module "anchor". 529 Site is overloaded
Signals that the site can not process the request.[62]

Pantheon Systems web platform

Used by the Pantheon Systems web platform.

Script error: No such module "anchor". 530 Site is frozen
Indicates a site that has been frozen due to inactivity.[63]

LinkedIn

Used by LinkedIn.

Script error: No such module "anchor". 999 Request denied
Related to being blocked/walled or unable to access their webpages without first signing in.[64]

Miscellaneous

Script error: No such module "anchor". Script error: No such module "anchor". 218 This is fine
An informal catch-all error condition, widely attributed to the Apache HTTP server to allow for the passage of message bodies through the server when the ProxyErrorOverride setting is enabled, though the status code and behavior is not part of any official Apache specification. The association between this status code and Apache has been attributed to unsourced additions to Wikipedia, which were subsequently picked up by other reference material, creating circular references.[65]
Script error: No such module "anchor". 598 Network read timeout error
An informal convention used by some HTTP proxies to signal a network read timeout behind the proxy to a client in front of the proxy.[66]
Script error: No such module "anchor". 599 Network Connect Timeout Error
An error used by some HTTP proxies to signal a network connect timeout behind the proxy to a client in front of the proxy.

See also

References

Page Template:Reflist/styles.css has no content.

  1. ↑ a b c Script error: No such module "citation/CS1".
  2. ↑ Script error: No such module "citation/CS1". 102 status code is deprecated
  3. ↑ Script error: No such module "citation/CS1".
  4. ↑ Script error: No such module "template wrapper".
  5. ↑ Script error: No such module "citation/CS1".
  6. ↑ Script error: No such module "citation/CS1".
  7. ↑ Script error: No such module "citation/CS1".
  8. ↑ Script error: No such module "citation/CS1".
  9. ↑ Script error: No such module "citation/CS1".
  10. ↑ a b c Script error: No such module "Citation/CS1".
  11. ↑ Script error: No such module "Citation/CS1".
  12. ↑ Script error: No such module "citation/CS1".
  13. ↑ Script error: No such module "citation/CS1".
  14. ↑ Script error: No such module "citation/CS1".
  15. ↑ Script error: No such module "citation/CS1".
  16. ↑ Script error: No such module "citation/CS1".
  17. ↑ Script error: No such module "citation/CS1".
  18. ↑ Script error: No such module "citation/CS1".
  19. ↑ a b Script error: No such module "citation/CS1".
  20. ↑ Script error: No such module "citation/CS1".
  21. ↑ Script error: No such module "citation/CS1".
  22. ↑ Script error: No such module "citation/CS1".
  23. ↑ Script error: No such module "citation/CS1".Template:Cbignore
  24. ↑ Script error: No such module "citation/CS1".
  25. ↑ Script error: No such module "citation/CS1".
  26. ↑ a b c Cite error: Script error: No such module "Namespace detect".Script error: No such module "Namespace detect".
  27. ↑ Script error: No such module "citation/CS1".
  28. ↑ Script error: No such module "citation/CS1".
  29. ↑ Script error: No such module "citation/CS1".
  30. ↑ Script error: No such module "citation/CS1".
  31. ↑ Script error: No such module "citation/CS1".
  32. ↑ Script error: No such module "citation/CS1".
  33. ↑ Script error: No such module "citation/CS1".
  34. ↑ Script error: No such module "citation/CS1".
  35. ↑ Script error: No such module "citation/CS1".
  36. ↑ Script error: No such module "citation/CS1".
  37. ↑ Script error: No such module "citation/CS1".
  38. ↑ "return" directive Script error: No such module "webarchive". (http_rewrite module) documentation.
  39. ↑ Script error: No such module "citation/CS1".
  40. ↑ Script error: No such module "citation/CS1".
  41. ↑ Script error: No such module "citation/CS1".
  42. ↑ Script error: No such module "citation/CS1".
  43. ↑ Script error: No such module "citation/CS1".
  44. ↑ Script error: No such module "citation/CS1".
  45. ↑ Script error: No such module "citation/CS1".
  46. ↑ Script error: No such module "citation/CS1".
  47. ↑ Script error: No such module "citation/CS1".
  48. ↑ Script error: No such module "citation/CS1".
  49. ↑ Script error: No such module "citation/CS1".
  50. ↑ Script error: No such module "citation/CS1".
  51. ↑ Script error: No such module "citation/CS1".
  52. ↑ a b c d e f Script error: No such module "citation/CS1".
  53. ↑ Script error: No such module "citation/CS1".
  54. ↑ Script error: No such module "citation/CS1".
  55. ↑ Script error: No such module "citation/CS1".
  56. ↑ Script error: No such module "citation/CS1".
  57. ↑ Script error: No such module "citation/CS1".
  58. ↑ Script error: No such module "citation/CS1".
  59. ↑ a b c d Script error: No such module "citation/CS1".
  60. ↑ a b Script error: No such module "citation/CS1".
  61. ↑ Script error: No such module "citation/CS1".
  62. ↑ Script error: No such module "citation/CS1".
  63. ↑ Script error: No such module "citation/CS1".
  64. ↑ Seen in 2017, 2024 and 2025 examples
  65. ↑ Script error: No such module "citation/CS1".
  66. ↑ Script error: No such module "citation/CS1".

Script error: No such module "Check for unknown parameters".

Script error: No such module "Side box".

Template:Error messages

Retrieved from "http://cosmopedia.co/index.php?title=List_of_HTTP_status_codes&oldid=6933772#304"