302 Http Error Message
Contents |
Status codes 301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable For Legal Reasons v t e The HTTP response status
302 Http Error Code
code 302 Found is a common way of performing URL redirection. An HTTP 302 http status response with this status code will additionally provide a URL in the location header field. The user agent
Http 404 Error Message
(e.g. a web browser) is invited by a response with this code to make a second, otherwise identical, request to the new URL specified in the location field. The HTTP/1.0 specification http error message header (RFC 1945) initially defined this code, and gives it the description phrase "Moved Temporarily". Many web browsers implemented this code in a manner that violated this standard, changing the request type of the new request to GET, regardless of the type employed in the original request (e.g. POST).[1] For this reason, HTTP/1.1 (RFC 2616) added the new status codes 303 and http error message 403 307 to disambiguate between the two behaviours, with 303 mandating the change of request type to GET, and 307 preserving the request type as originally sent. Despite the greater clarity provided by this disambiguation, the 302 code is still employed in web frameworks to preserve compatibility with browsers that do not implement the HTTP/1.1 specification.[2] As a consequence, the update of RFC 2616 changes the definition to allow user agents to rewrite POST to GET.[3] Contents 1 Example 2 See also 3 References 4 External links Example[edit] Client request: GET /index.html HTTP/1.1 Host: www.example.com Server response: HTTP/1.1 302 Found Location: http://www.iana.org/domains/example/ See also[edit] List of HTTP status codes HTTP 301 - Permanent Redirect References[edit] ^ Lawrence, Eric. "HTTP Methods and Redirect Status Codes". EricLaw's IEInternals blog. Retrieved 2011-08-20. ^ "Request and response objects | Django documentation | Django". Docs.djangoproject.com. Retrieved 2014-06-23. ^ "draft-ietf-httpbis-p2-semantics-26 - Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content". Tools.ietf.org. Retrieved 2014-06-23. External links[edit] 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 Name
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting
Http Error Message 403 Forbidden From Detected
ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join html status 302 the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a
Ftp Error Message
minute: Sign up What does HTTP/1.1 302 mean exactly? up vote 26 down vote favorite 10 Some article I read once said that it means jumping (from one URI to another), but I detected this "302" even when there was actually https://en.wikipedia.org/wiki/HTTP_302 no jumping at all! http redirect http-headers http-status-code-302 share|improve this question edited Jan 14 at 15:01 CubeJockey 2,12071629 asked Jun 10 '09 at 0:06 omg 34k102235313 There might be some good information on this here in the wc3.org documentation. –Copas Jun 10 '09 at 0:09 2 Pay close attention: example.com example.com and example.com are logically-distinct, and a site wishing to be accessed via a single URL may redirect from one to another in order to achieve this. Of course, http://stackoverflow.com/questions/973098/what-does-http-1-1-302-mean-exactly 302 redirects are a poor choice for this... but you may well have seen similarly subtle variations. –Shog9♦ Jun 10 '09 at 0:18 1 Sorry, all my knowledge of HTTP error codes come from here: thinkgeek.com/tshirts-apparel/womens/6792 (doht! 403 again) –kenj0418 Jun 10 '09 at 0:25 add a comment| 8 Answers 8 active oldest votes up vote 19 down vote A 302 redirect means that the page was temporarily moved, while a 301 means that it was permanently moved. 301s are good for SEO value, while 302s aren't because 301s instruct clients to forget the value of the original URL, while the 302 keeps the value of the original and can thus potentially reduce the value by creating two, logically-distinct URLs that each produce the same content (search engines view them as distinct duplicates rather than a single resource with two names). share|improve this answer edited Jun 10 '09 at 0:15 Shog9♦ 108k28183217 answered Jun 10 '09 at 0:10 CodeMonkey1313 6,4801451104 add a comment| up vote 7 down vote A simple way of looking at HTTP 301 vs. 302 redirects is: Suppose you have a bookmark to "http://sample.com/sample". You use a browser to go there. A 302 redirect to a different URL at this point would mean that you should keep your bookmark to "http://sample.com/sample". This is because the destination URL may change in the future. A 301 redirect to a different URL would mean that your bookmark should change to point to th
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 line. There are no required headers for this class of status code. https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 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 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 (Continue) status message. Unexpected 1xx status responses MAY be ignored by a user agent. Proxies MUST forward 1xx responses, unless the connection error message 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 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 http error message 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 real-time, synchronous protocol might be advantageous when delivering resources that use such features. 10.2 Successful 2xx This class of status code indicates that the client's request was successfully received, understood, and accepted. 10.2.1 200 OK The request has succeeded. The information returned with the response is dependent on the method used in the request, for example: GET an entity corresponding to the requested resource is sent in the response;