Re: Browser Interpretation of Location: Header

>Jim Killian asked on www-talk what a client should do on receiving a 302
>redirect from a POST operation.  Should the client repost the data to
>the new location (ie, 302 means the script has moved) or GET the new
>Location (ie 302 means the result of POSTing is somewhere else)?

This problem has already been solved by making 301 and 302 perform
a same-method redirection (after user approval if not GET) and
303 See Other be a "any method" => GET redirection.

 ....Roy T. Fielding  Department of ICS, University of California, Irvine USA
                      Visiting Scholar, MIT/LCS + World-Wide Web Consortium
                      (fielding@w3.org)                (fielding@ics.uci.edu)