Http Error Code Meanings
Contents |
response. 10.1 Informational 1xx This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty http status code 400 line. There are no required headers for this class of status code. Since
Http Status Codes Cheat Sheet
HTTP/1.0 did not define any 1xx status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client http response example except under experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if the client does not expect a 100
Http Code 302
(Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not http 422 forward the corresponding 100 (Continue) response(s).) 10.1.1 100 Continue The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code. 10.1.2 101 Switching Protocols The server understands and is willing to comply with the client's request, via the Upgrade message header field (section 14.42), for a change in the application protocol being used on this connection. 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. The protocol SHOULD be switched only when it is advantageous to do so. For example, switching to a newer version of HTTP is advantageous over older versions, and switching to a
consisting only of the Status-Line and optional headers, and is terminated by an empty line. There are no required headers for this class of status code. Since HTTP/1.0 did not define any 1xx
Http 403
status codes, servers MUST NOT send a 1xx response to an HTTP/1.0 client except under
Http 404
experimental conditions. A client MUST be prepared to accept one or more 1xx status responses prior to a regular response, even if http 500 the client does not expect a 100 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection between the proxy and its client has https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html been closed, or unless the proxy itself requested the generation of the 1xx response. (For example, if a proxy adds a "Expect: 100-continue" field when it forwards a request, then it need not forward the corresponding 100 (Continue) response(s).) Wikipedia Request received, continuing process. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any http://www.restapitutorial.com/httpstatuscodes.html 1xx status codes, servers must not send a 1xx response to an HTTP/1.0 client except under experimental conditions. 100 Continue The client SHOULD continue with its request. This interim response is used to inform the client that the initial part of the request has been received and has not yet been rejected by the server. The client SHOULD continue by sending the remainder of the request or, if the request has already been completed, ignore this response. The server MUST send a final response after the request has been completed. See section 8.2.3 for detailed discussion of the use and handling of this status code. Wikipedia This means that the server has received the request headers, and that 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). If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. To have a server check if the request could be accepted based on the request's headers alone, a client must send Expect: 100-continue as a header in its initial request and check if a 100 Continue status code is received in response before continuing (or receive 417
& Guides Learn the Web Tutorials References Developer Guides Accessibility Game development ...more docs Mozilla Docs Add-ons Firefox WebExtensions Developer ToolsFeedback Get Firefox help Get web development help Join https://developer.mozilla.org/en-US/docs/Web/HTTP/Status the MDN community Report a content problem Report a bug Search Search http://www.seocentro.com/articles/apache/http-status-codes.html Languages 日本語 (ja) 한국어 (ko) Русский (ru) 中文 (简体) (zh-CN) 正體中文 (繁體) (zh-TW) Add a translation Edit Advanced Advanced History Print this article MDN Web technology For developers HTTP HTTP response status codes Your Search Results fscholz sivasain arulnithi rctgamer3 groovecoder dovgart Sheppy fusionchess HTTP response status codes In This Article Information responsesSuccessful http status responsesRedirection messagesClient error responsesServer error responses HTTP response status codes indicate whether a specific HTTP request has been successfully completed. Responses are grouped in five classes: informational responses, successful responses, redirects, client errors, and servers errors. Information responses 100 Continue This interim response indicates that everything so far is OK and that the client should continue with the request or ignore it if it is already finished. http status code 101 Switching Protocol This code is sent in response to an Upgrade: request header by the client, and indicates that the protocol the server is switching too. It was introduced to allow migration to an incompatible protocol version, and is not in common use. Successful responses 200 OK The request has succeeded. The meaning of a success varies depending on the HTTP method: GET: The resource has been fetched and is transmitted in the message body. HEAD: The entity headers are in the message body. POST: The resource describing the result of the action is transmitted in the message body. 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 is typically the response sent after a PUT request. 202 Accepted The request has been received but not yet acted upon. It is non-committal, meaning that there is no way in HTTP to later send an asynchronous response indicating the outcome of processing the request. It is intended for cases where another process or server handles the request, or for batch processing. 203 Non-Authoritative Information This respons
Friendly Test » Keyword Density » Keyword Generator » MozRank Checker » Alexa Ranking » PageRank Check » Twitter Card Generator » Facebook Open Graph » Social Media Shares » Keyword Analyzer Online Tools » QR Code Generator » IP Geolocation » My IP Address » Server Headers Check » Share Link Generator » Minify JavaScript » Minify CSS » HTML Encoder » URL Encoder HTTP Status and Error Codes Explained The following is a list of HTTP response status codes and standard associated phrases, intended to give a short textual description of the status. 1xx Informational 2xx Success 3xx Redirection 4xx Client Error 5xx Server Error 1xx InformationalRequest received, continuing process. top Code Status Explanation 100 Continue The request has been completed and the rest of the process can continue. 101 Switching Protocols When requesting a page, a browser might receive a statis code of 101, followed by an "Upgrade" header showing that the server is changing to a different version of HTTP. 2xx SuccessThe action was successfully received, understood, and accepted. top Code Status Explanation 200 OK Standard response for HTTP successful requests. 201 Created When new pages are created by posted form data or by a CGI process, this is confirmation that it worked. 202 Accepted The client's request was accepted, though not yet processed. 203 Non-Authorative Information The information contained in the entity header is not from the original site, but from a third party server. 204 No Content If you click a link which has no target URL, this response is elicited by the server. It's silent and doesn't warn the user about anything. 205 Reset Content This allows the server to reset any content returned by a CGI. 206 Partial Content The requested file wasn't downloaded entirely. This is returned when the user presses the stop button before a page is loaded, for example. 3xx RedirectionThe client must take additional action to complete the request. top Code Status Explanation 300 Multiple Choices The requested address refers to more than one file. Depending on how the server is configured, you get an error or a choice of which page you want. 301 Moved Permanently If the server is set up properly it will automatically redirect the reader to the new location of the file. 302 Moved Temporarily Page has been moved temporarily, and the new URL is av