Subsequent requests by the client are permissible. Did the user type in the wrong URL? Cloudflare Cloudflare's reverse proxy service expands the 5xx series of errors space to signal issues with the origin server. 520 Unknown Error The 520 error is used as a "catch-all response for when the origin server returns something unexpected", listing connection resets, large headers, and empty or invalid responses as common triggers. 521 Web Server Is Down The origin server has refused the connection from Cloudflare. 522 Connection Timed Out Cloudflare could not negotiate a TCP handshake with 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. 524 A Timeout Occurred Cloudflare was able to complete a TCP connection to the origin server, but did not receive a timely HTTP response. 525 SSL Handshake Failed Cloudflare could not negotiate a SSL/TLS handshake with the origin server. 526 Invalid SSL Certificate Cloudflare could not validate the SSL/TLS certificate that the origin server presented. 527 Railgun Error A 527 error indicates that the requests timeout or failed after the WAN connection has been established. See also Custom error pages List of FTP server return codes List of HTTP header fields Notes ^ Italicised words and phrases such as must and should represent interpretation guidelines as given by RFC 2119 References ^ "Hypertext Transfer Protocol -- HTTP/1.1". If the 307 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued. http://orgias.org/http-status/http-error-codes-301.html
No URL found. Retrieved 2016-01-09. ^ "Railgun Listener to Origin Error". Also, note that captive portals using this status code on an SSL or TLS connection (commonly, port 443) will generate a certificate error on the client. Google Books.
about tech. Msdn.microsoft.com. ArcGIS Server SOAP SDK. ^ "HTTP Error Codes and Quick Fixes". Http Code 302 Cloudflare.
This response SHOULD contain an appropriate precondition or postcondition code, such as 'lock-token-submitted' or 'no-conflicting-lock'. Often caused by misspellings of URLs. 405 Method Not Allowed The method you are using to access the file is not allowed. 406 Not Acceptable The requested file exists but cannot be used as the client system doesn't understand the format the file is configured for. 407 Proxy Authentication Required The request must be authorised before it can take place. 408 Request Timed Out The server took longer than its allowed time to process the request. GetStatusCode. http://www.websitepulse.com/kb/3xx_http_status_codes.html Wikipedia The server is unable to store the representation needed to complete the request. 508 Loop Detected (WebDAV) The 508 (Loop Detected) status code indicates that the server terminated an operation because it encountered an infinite loop while processing a request with "Depth: infinity".
Unless it was a HEAD request, the response SHOULD include an entity containing a list of available entity characteristics and location(s) from which the user or user agent can choose the one most appropriate. Http 422 The 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields. 10.2.6 205 Reset Content The server has fulfilled the request and the user agent SHOULD reset the document view which caused the request to be sent. Retrieved 16 October 2015. ^ "202". RFC 2774.
DNS) it needed to access in attempting to complete the request. Previously called "Request Entity Too Large". 414 URI Too Long (RFC 7231) The URI provided was too long for the server to process. Http Status Code The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant. Http Code 403 The client SHOULD NOT repeat the request without modifications. 10.4.2 401 Unauthorized The request requires user authentication.
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. 417 Expectation Failed The server cannot meet the requirements of the Expect request-header field. 418 I'm a teapot (RFC 2324) 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. weblink Content developers should be aware that there might be clients that implement such a fixed limitation. 10.3.1 300 Multiple Choices The requested resource corresponds to any one of a set of representations, each with its own specific location, and agent- driven negotiation information (section 12) is being provided so that the user (or user agent) can select a preferred representation and redirect its request to that location. The entity returned with this response SHOULD include an indication of the request's current status and either a pointer to a status monitor or some estimate of when the user can expect the request to be fulfilled. Used for conditional GET calls to reduce band-width usage. Http Response Example
This error is given when Windows Parental Controls are turned on and are blocking access to the given webpage. 451 Unavailable For Legal Reasons Wikipedia Intended to be used when resource access is denied for legal reasons, e.g. Otherwise (i.e., the conditional GET used a weak validator), the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. These response codes are applicable to any request method. 500 Internal Server Error The server encountered an unexpected condition which prevented it from fulfilling the request. navigate here Does the server configuration have the correct document root location?
An HTTP Extension Framework. Http 502 June 1999. Wikipedia The server cannot meet the requirements of the Expect request-header field. 418 I'm a teapot (RFC 2324) Wikipedia 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.
This response is only cacheable if indicated by a Cache-Control or Expires header field. Retrieved 7 March 2015. ^ "Server Error Codes". Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. Http 504 https://tools.ietf.org/html/rfc4918.
nginx 1.9.5 source code. Retrieved 16 October 2015. ^ "Mozilla Bugzilla Bug 187996: Strange behavior on 305 redirect". IETF. 2014. http://orgias.org/http-status/http-error-codes-404-403.html Cloudflare.
Its purpose is to allow a server to accept a request for some other process (perhaps a batch-oriented process that is only run once per day) without requiring that the user agent's connection to the server persist until the process is completed. Retrieved 2016-10-12. Stack Overflow. If a Content-Length header field is present in the response, its value MUST match the actual number of OCTETs transmitted in the message-body. - Date - ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request - Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same variant If the 206 response is the result of an If-Range request that used a strong cache validator (see section 13.3.3), the response SHOULD NOT include other entity-headers.
In contrast to 302, the request method should not be changed when reissuing the original request. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URI(s). In a GET request, the response will contain an entity corresponding to the requested resource. Retrieved October 24, 2009. ^ "Enum HttpStatus".
Retrieved October 11, 2009. ^ a b "Using token-based authentication". Wikipedia The server failed to fulfill an apparently valid request. The response 417 Expectation Failed indicates the request should not be continued. 101 Switching Protocols The requester has asked the server to switch protocols and the server has agreed to do so. 102 Processing (WebDAV; RFC 2518) A WebDAV request may contain many sub-requests involving file operations, requiring a long time to complete the request. If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials.