Search This Blog

Thursday, June 23, 2011

HTTP 302 - Explained

The 302 redirection is described in RFC2616: “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“.
For example, using a 302 redirection from to, means that, although the page is temporarily redirected to the special action promotional page, the preferred address to be used in the future remains redirects should be used for temporary redirections.
Browsers automatically follow these redirections. They also display the temporary address in the address bar.
The same address pointed to by the redirection will eventually be saved in the browser favorites. Although this is not what should be done according to RFC2616, it does not seem to create many problems in the real world.
Related Articles

No comments:

Post a Comment