What does the 302 server response code signify? Here is some info on this.
Quote: The HTTP response status code 302 Found is the most common way of performing a redirection.[citation needed]
It is an example of industry practice contradicting the standard HTTP/1.0 specification (RFC 1945), which required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented it as a 303 See Other, i.e. changing the request type to GET regardless of what it had been originally. Therefore, HTTP/1.1 added status codes 303 and 307 to disambiguate between the two behaviours. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.
This status code should be used with the location header Source: http://en.wikipedia.org/wiki/HTTP_302
There examples on the page also. Quote: The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. 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).
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. These are the ideas of W3.org the link of that particular page has been given below, For more information You can directly visit that page itself. There you will find some more in formations related to this.
302 server response code
Quote: The HTTP response status code 302 Found is the most common way of performing a redirection.[citation needed]
It is an example of industry practice contradicting the standard HTTP/1.0 specification (RFC 1945), which required the client to perform a temporary redirect (the original describing phrase was "Moved Temporarily"), but popular browsers implemented it as a 303 See Other, i.e. changing the request type to GET regardless of what it had been originally. Therefore, HTTP/1.1 added status codes 303 and 307 to disambiguate between the two behaviours. However, the majority of Web applications and frameworks still use the 302 status code as if it were the 303.
This status code should be used with the location header Source: http://en.wikipedia.org/wiki/HTTP_302
There examples on the page also. Quote: The requested resource resides temporarily under a different URI. Since the redirection might be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. This response is only cacheable if indicated by a Cache-Control or Expires header field.
The temporary URI SHOULD be given by the Location field in the response. 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).
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. These are the ideas of W3.org the link of that particular page has been given below, For more information You can directly visit that page itself. There you will find some more in formations related to this.
302 server response code