Weblabor

302 Found
A 302 Found response is similar to the 301 Moved Permanently response, except that the new location should only be used for this request. The new resource location is indicated in a Location header, and the client should issue the same request method for the new resource as it used for the request that resulted in this response.

Note

Nearly all known Web clients do not adhere correctly to the HTTP definition with regard to this response code. Regardless of which request method is used in the initial HTTP request, the request method used to fetch the resource in its new location is GET. To allow for a status code that explicitly intends for this behavior, the HTTP/1.1 definition includes the 303 See Other status code, which specifies that a GET request method must be used for the resource in its new location. Thus, in practice, both 302 Found and 303 See Other are handled in the same manner. Because some older Web clients do not understand the 303 See Other status code, most current implementations of protocol-level redirection in which a GET request is desired rely on the 302 Found status code.



This response is what many server-side scripting languages such as PHP and ColdFusion currently use when a developer manually uses a Location header in the code (although discussion is underway for PHP to allow the developer to override the response status code). For example:

<?
header("Location: http://httphandbook.org/");
?>
This will result in a response similar to the following:

HTTP/1.1 302 Found
Date: Tue, 21 May 2002 12:34:56 GMT
Location: http://httphandbook.org/
Transfer-Encoding: chunked
Content-Type: text/html

0