Retrieved 16 October 2015. ^ a b c d "Hypertext Transfer Protocol (HTTP) Status Code Registry". This response is primarily intended to allow input for actions to take place via user input, followed by a clearing of the form in which the input is given so that the user can easily initiate another input action. Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. Microsoft. 2009. navigate here
If the condition is temporary, the server SHOULD include a Retry- After header field to indicate that it is temporary and after what time the client MAY try again. 10.4.15 414 Request-URI Too Long The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret. If the user is unexpectedly getting a 403 Forbidden error, ensure that it is not being caused by your .htaccess settings. This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent's active view. Moved 301 The data requested has been assigned a new URI, the change is permanent. (N.B. https://en.wikipedia.org/wiki/List_of_HTTP_status_codes
Not observing these limitations has significant security consequences. 10.3.7 306 (Unused) The 306 status code was used in a previous version of the specification, is no longer used, and the code is reserved. 10.3.8 307 Temporary Redirect The requested resource resides temporarily under a different URI. This response is only cacheable if indicated by a Cache-Control or Expires header field. Request for Comments. Depending upon the format and the capabilities of the user agent, selection of the most appropriate choice MAY be performed automatically.
For example, the client uploads an image as image/svg+xml, but the server requires that images use a different format. 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. Since HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under experimental conditions. A 201 response MAY contain an ETag response header field indicating the current value of the entity tag for the requested variant just created, see section 14.19. Http Code 302 Wikipedia The server does not support the HTTP protocol version used in the request. 506 Variant Also Negotiates (Experimental) The 506 status code indicates that the server has an internal configuration error: the chosen variant resource is configured to engage in transparent content negotiation itself, and is therefore not a proper end point in the negotiation process.
Google. 2015. Http Status Codes Cheat Sheet External links Wikimedia Commons has media related to HTTP. Ideally, the response entity would include enough information for the user or user agent to fix the problem; however, that might not be possible and is not required. https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Note: Many pre-HTTP/1.1 user agents do not understand the 303 status.
In a GET request, the response will contain an entity corresponding to the requested resource. Http Code 403 External links Wikimedia Commons has media related to HTTP. This should be used when a resource has been intentionally removed and the resource should be purged. Transparent Content Negotiation in HTTP.
A user agent may automatically redirect a request. http://orgias.org/http-code/http-error-code-602.html If the 302 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. 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. 10.4 Client Error 4xx The 4xx class of status code is intended for cases in which the client seems to have erred. a malformed .htaccess file) or missing packages (e.g. Http 422
TRACE: The message body contains the request message as received by the server 201 Created The request has succeeded and a new resource has been created as a result of it. This has the same semantic than the 302 Found HTTP response code, with the exception that the user agent must not change the HTTP method used: if a POST was used in the first request, a POST must be used in the second request. 308 Permanent Redirect This means that the resource is now permanently located at another URI, specified by the Location: HTTP Response header. The server will switch protocols to those defined by the response's Upgrade header field immediately after the empty line which terminates the 101 response. http://orgias.org/http-code/http-200-error-code.html I added a link in the description below.
Retrieved October 11, 2009. ^ a b "Using token-based authentication". Http 404 IETF. The set presented MAY be a subset or superset of the original version.
General Troubleshooting Tips When using a web browser to test a web server, refresh the browser after making server changes Check server logs for more details about how the server is handling the requests. If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions. June 1999. Http 502 GitHub.
HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication". Using this saves bandwidth and reprocessing on both the server and client, as only the header data must be sent and received in comparison to the entirety of the page being re-processed by the server, then sent again using more bandwidth of the server and client. There must be no body on the response. 305 Use Proxy The requested resource MUST be accessed through the proxy given by the Location field. http://orgias.org/http-code/http-207-error-code.html This method exists primarily to allow the output of a POST-activated script to redirect the user agent to a selected resource.
Hyper Text Coffee Pot Control Protocol (HTCPCP/1.0). Retrieved October 24, 2009. ^ ikitommi; Daraen. "metosin/ring-http-response". It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some additional commonly used codes. The body may be preceded by the following additional fields as listed.
Retrieved 16 October 2015. ^ "RFC2616 on status 414". A user agent should detect and intervene to prevent cyclical redirects. 300 Multiple Choices Indicates multiple options for the resource from which the client may choose (via agent-driven content negotiation). HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication". IETF.
Wikipedia Defined in drafts of "WebDAV Advanced Collections Protocol", but not present in "Web Distributed Authoring and Versioning (WebDAV) Ordered Collections Protocol". 426 Upgrade Required Reliable, interoperable negotiation of Upgrade features requires an unambiguous failure signal. Note: Some sites 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. Upon receiving a 410 status code, the client should not request the resource in the future. Oracle.
If the server in question is a reverse proxy server, such as a load balancer, here are a few things to check: The backend servers (where the HTTP requests are being forwarded to) are healthy The reverse proxy is configured properly, with the proper backends specified The network connection between the backend servers and reverse proxy server is healthy. 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). Wikipedia In this case, the request should be repeated with another URI; however, future requests can still use the original URI. By requiring requests to be conditional, the server can assure that clients are working with the correct copies.
RFC 3229. This response is cacheable unless indicated otherwise. This most common cause for this error is server misconfiguration (e.g. Since HTTP/1.0 did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 client except under experimental conditions. 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; for example, a POST request).
Wikipedia The server timed out waiting for the request. about tech. Retrieved 16 October 2015. ^ "RFC2616 on status 414". Originally meant "Subsequent requests should use the specified proxy." 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.