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. 10.4.13 412 Precondition Failed The precondition given in one or more of the request-header fields evaluated to false when it was tested on the server. 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. The server MUST send a final response after the request has been completed. Retrieved October 11, 2009. ^ a b "Using token-based authentication". his comment is here
Retrieved 16 October 2015. ^ "202". So, for example, submitting a form to a permanently redirected resource may continue smoothly. 4xx Client Error 404 error on German Wikipedia The 4xx class of status code is intended for situations in which the client seems to have erred. This behavior is beneficial because it reduces duplicate content. Used when the requested resource is not found, whether it doesn't exist or if there was a 401 or 403 that, for security reasons, the service wants to mask. 405 Method Not Allowed The method specified in the Request-Line is not allowed for the resource identified by the Request-URI.
IETF. These status codes are applicable to any request method. Transparent Content Negotiation in HTTP. 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. 415 Unsupported Media Type The request entity has a media type which the server or resource does not support.
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. The phrases used are the standard wordings, but any human-readable alternative can be provided. This is the appropriate response when the server does not recognize the request method and is not capable of supporting it for any resource. 10.5.3 502 Bad Gateway The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request. 10.5.4 503 Service Unavailable The server is currently unable to handle the request due to a temporary overloading or maintenance of the server. 302 Police Code If known, the length of the delay MAY be indicated in a Retry-After header.
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. Note: RFC 2068 was not clear that 305 was intended to redirect a single request, and to be generated by origin servers only. For example, this code could be used to present multiple video format options, to list files with different extensions, or to suggest word sense disambiguation. 301 Moved Permanently This and all future requests should be directed to the given URI. 302 Found This is an example of industry practice contradicting the standard. External links RFC 2616 (HTTP 1.1) RFC 1945 (HTTP 1.0) Retrieved from "https://en.wikipedia.org/w/index.php?title=HTTP_302&oldid=732065033" Categories: Hypertext Transfer Protocol status codes 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 BoarischBahasa IndonesiaPortuguêsСрпски / srpskiУкраїнська中文 Edit links This page was last modified on 29 July 2016, at 10:43.
Retrieved 16 October 2015. ^ "RFC 7231, Section 6.3.4.". ^ "RFC 7230, Section 5.7.2.". ^ Simmance, Chris. "Server Response Codes And What They Mean". Http 302 Error Fix 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. The request MAY be resubmitted after reducing the size of the request header fields. 451 Unavailable For Legal Reasons The user requests an illegal resource, such as a web page censored by a government.
The server MAY close the connection to prevent the client from continuing the request. Source: RFC7231 Section 6.4.3 302 Code References Rails HTTP Status Symbol :found Go HTTP Status Constant http.StatusFound Symfony HTTP Status Constant Response::HTTP_FOUND Python2 HTTP Status Constant httplib.FOUND Python3+ HTTP Status Constant http.client.FOUND Python3.5+ HTTP Status Constant http.HTTPStatus.FOUND← Return to httpstatuses.com CheckUpDown Tweet HTTP Error 302 - Moved temporarily Introduction Your Web server thinks that your URL has been temporarily redirected to another URL. Http 302 Found The server MUST send a final response after the request has been completed. Http 301 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 action required MAY be carried out by the user agent without interaction with the user if and only if the method used in the second request is GET or HEAD. this content IETF. 2014. Cloudflare. April 2015. Http 302 Vs 301
The server SHOULD generate a Location header field in the response containing a URI reference for the different URI. If the server does not know, or has no facility to determine, whether or not the condition is permanent, the status code 404 (Not Found) SHOULD be used instead. Internet Engineering Task Force. weblink HTTP access authentication is explained in "HTTP Authentication: Basic and Digest Access Authentication" . 10.4.9 408 Request Timeout The client did not produce a request within the time that the server was prepared to wait.
with a HTML form). Http Status Codes Cheat Sheet Retrieved November 13, 2013. ^ "2.2.6 449 Retry With Status Code". Retrieved 2014-06-23.
If the request body is large, sending it to a server when a request has already been rejected based upon inappropriate headers is inefficient. Where are sudo's insults stored? 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. 100 Continue The client SHOULD continue with its request. check over here The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field.
Common causes are a server that is down for maintenance or that is overloaded. Wikipedia A generic error message, given when no more specific message is suitable.