Wikipedia The server has fulfilled a GET request for the resource, and the response is a representation of the result of one or more instance-manipulations applied to the current instance. 3xx Redirection This class of status code indicates that further action needs to be taken by the user agent in order to fulfill the request. Document Tags and Contributors Tags: HTTP Status codes Contributors to this page: fscholz, sivasain, arulnithi, rctgamer3, groovecoder, dovgart, Sheppy, fusionchess Last updated by: fscholz, Jul 28, 2016, 6:30:22 AM See also HTTP Guides: Resources and URIs Identifying resources on the Web Data URIs Introduction to MIME Types Complete list of MIME Types Choosing between www and non-www URLs Basics of HTTP Overview of HTTP Evolution of HTTP HTTP Messages A typical HTTP session Connection management in HTTP/1.x Redirections in HTTP Conditional requests Content negotiation HTTP cookies HTTP access control (CORS) Resources and specifications References: HTTP headers Accept-RangesAgeCache-ControlConnectionContent-DispositionContent-EncodingContent-LanguageContent-LengthContent-LocationContent-Security-PolicyContent-TypeDateETagExpiresFromHostIf-MatchIf-Modified-SinceIf-None-MatchIf-RangeIf-Unmodified-SinceKeep-AliveLast-ModifiedLocationPragmaRefererRetry-AfterServerTETrailerTransfer-EncodingUser-AgentVaryViaWarningX-Frame-Options HTTP request methods GETHEADPOST HTTP response status codes 100 Continue200 OK201 Created204 No Content206 Partial Content301 Moved Permanently302 Found303 See Other304 Not Modified307 Temporary Redirect308 Permanent Redirect404 Not Found410 Gone412 Precondition Failed451 Unavailable For Legal Reasons500 Internal Server Error501 Not Implemented502 Bad Gateway503 Service Unavailable504 Gateway Timeout © 2005-2016 Mozilla Developer Network and individual contributors. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. The server MAY close the connection to prevent the client from continuing the request. this contact form
Retrieved 16 October 2015. ^ Brown, Kevin; CRS... "getting 304 response even with django-cors-headers". It is not intended to encouraged deployment of captive portals, only to limit the damage caused by them. The two mandatory methods, GET and HEAD, must never be disabled and should not return this error code. 406 Not Acceptable This response is sent when the web server, after performing server-driven content negotiation, doesn't find any content following the criteria given by the user agent. 407 Proxy Authentication Required This is similar to 401 but authentication is needed to be done by a proxy. 408 Request Timeout This response is sent on an idle connection by some servers, even without any previous request by the client. Except this condition, 200 OK response should be preferred instead of this response. 204 No Content There is no content to send for this request, but the headers may be useful. https://developer.mozilla.org/en-US/docs/Web/HTTP/Status
Wikipedia A generic error message, given when no more specific message is suitable. 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. Hypertext Transfer Protocol -- HTTP/1.1.
When a server receives that request, it sends back an HTTP Response, with information for the client. There are no required headers for this class of status code. The only methods that servers are required to support (and therefore that must not return this code) are GET and HEAD. 502 Bad Gateway This error response means that the server, while working as a gateway to get a response needed to handle the request, got an invalid response. 503 Service Unavailable The server is not ready to handle the request. Http Response Example 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. 429 Too Many Requests The user has sent too many requests in a given amount of time ("rate limiting"). 431 Request Header Fields Too Large The server is unwilling to process the request because its header fields are too large.
Unexpected 1xx status responses MAY be ignored by a user agent. Http Error Wordpress Wikipedia The server detected an infinite loop while processing the request (sent in lieu of 208). 509 Bandwidth Limit Exceeded (Apache) Wikipedia This status code, while used by many servers, is not specified in any RFCs. 510 Not Extended The policy for accessing the resource has not been met in the request. https://tools.ietf.org/html/rfc2774. Retrieved January 8, 2015. ^ "ngx_http_request.h".
If the response is the result of an If-Range request that used a weak validator, the response MUST NOT include other entity-headers; this prevents inconsistencies between cached entity-bodies and updated headers. Http 422 New changes in the URI might be made in the future. Retrieved May 1, 2012. ^ Bray, T. (February 2016). "An HTTP Status Code to Report Legal Obstacles". The server MUST send an Upgrade header field in a 426 response to indicate the required protocol(s) (Section 6.7 of [RFC7230]). 428 Precondition Required The origin server requires the request to be conditional.
https://tools.ietf.org/html/rfc4918. http://www.restapitutorial.com/httpstatuscodes.html RFC 2774. Http Status Codes Cheat Sheet If the request method was not HEAD and the server wishes to make public why the request has not been fulfilled, it SHOULD describe the reason for the refusal in the entity. Http Code 403 By requiring requests to be conditional, the server can assure that clients are working with the correct copies.
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). http://orgias.org/http-code/html-web-error-codes.html Wikipedia Further extensions to the request are required for the server to fulfill it. 511 Network Authentication Required The 511 status code indicates that the client needs to authenticate to gain network access. DELETE). 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. This may be, for example, because the client asked for the 800th-900th bytes of a document, but the document was only 200 bytes long.417 - Expectation FailedThe 417 status code means that the server was unable to properly complete the request. Http Code 302
If the 301 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. In such cases the client may time-out the connection while waiting for a response. Retrieved November 13, 2013. ^ "2.2.6 449 Retry With Status Code". http://orgias.org/http-code/html-error-codes-400.html https://tools.ietf.org/html/rfc2295.
Retrieved 16 October 2015. ^ "diff --git a/linkchecker.module b/linkchecker.module". Http 404 The original intention was that this code might be used as part of some form of digital cash or micropayment scheme, but that has not happened, and this code is not usually used. HEAD: The entity headers are in the message body.
This is used by advanced caching tools, when a user agent requests only a small part of a page, and just that section is returned. If a 304 response indicates an entity not currently cached, then the cache MUST disregard the response and repeat the request without the conditional. Likewise, user agents should display any included entity to the user. Http 502 Wikipedia The request is larger than the server is willing or able to process. 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.
Bad command or file name Halt and Catch Fire HTTP 418 Out of memory Lists List of HTTP status codes List of FTP server return codes Related Kill screen Spinning pinwheel Windows wait cursor Retrieved from "https://en.wikipedia.org/w/index.php?title=List_of_HTTP_status_codes&oldid=744546936" Categories: Hypertext Transfer Protocol status codesInternet-related listsHidden categories: All articles with unsourced statementsArticles with unsourced statements from July 2016Articles with unsourced statements from August 2016Commons category without a link on WikidataOfficial website missing URLUse mdy dates from November 2012 Navigation menu Personal tools Not logged inTalkContributionsCreate accountLog in Namespaces Article Talk Variants Views Read Edit View history More Search Navigation Main pageContentsFeatured contentCurrent eventsRandom articleDonate to WikipediaWikipedia store Interaction HelpAbout WikipediaCommunity portalRecent changesContact page Tools What links hereRelated changesUpload fileSpecial pagesPermanent linkPage informationWikidata itemCite this page Print/export Create a bookDownload as PDFPrintable version Languages العربيةČeštinaDeutschEspañolفارسیFrançais한국어Bahasa IndonesiaÍslenskaItalianoעבריתქართულიBahasa MelayuNederlands日本語Norsk bokmålPolskiPortuguêsРусскийСрпски / srpskiSvenskaไทยTürkçeУкраїнська中文 Edit links This page was last modified on 15 October 2016, at 23:22. 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. For example, including local annotation information about the resource might result in a superset of the metainformation known by the origin server. his comment is here Therefore, this same URI should be used by the client in future requests. 303 See Other Server sent this response to directing client to get requested resource to another URI with an GET request. 304 Not Modified This is used for caching purposes.
In contrast to 302, the request method should not be changed when reissuing the original request. However, this specification does not define any standard for such automatic selection. Retrieved 16 October 2015. ^ "202". The origin server MUST create the resource before returning the 201 status code.
HEAD: The entity headers are in the message body. Note: RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. If the client is sending data, a server implementation using TCP SHOULD be careful to ensure that the client acknowledges receipt of the packet(s) containing the response, before the server closes the input connection. The new permanent URI SHOULD be given by the Location field in the response.
Wikipedia The server successfully processed the request, but is not returning any content. The 204 response MUST NOT include a message-body, and thus is always terminated by the first empty line after the header fields. In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type. Tools.ietf.org.
Note: When automatically redirecting a POST request after receiving a 301 status code, some existing HTTP/1.0 user agents will erroneously change it into a GET request. Content is available under these licenses. Wikipedia The server was acting as a gateway or proxy and received an invalid response from the upstream server. 503 Service Unavailable The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. The client MAY repeat the request if it adds a valid Content-Length header field containing the length of the message-body in the request message.
The response MAY include new or updated metainformation in the form of entity-headers, which if present SHOULD be associated with the requested variant. These response codes are applicable to any request method. 500 Internal Server Error A generic error message, given when an unexpected condition was encountered and no more specific message is suitable. 501 Not Implemented The server either does not recognize the request method, or it lacks the ability to fulfill the request. An HTTP Extension Framework. Not observing these limitations has significant security consequences.
Retrieved 16 October 2015. ^ "RFC2616 on status 413".