W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > September to December 1995

Re: Browser Interpretation of Location: Header

From: Roy Fielding <fielding@beach.w3.org>
Date: Sat, 02 Sep 1995 16:48:58 -0400
Message-Id: <199509022048.QAA03554@beach.w3.org>
To: lilley <lilley@afs.mcc.ac.uk>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
>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)
Received on Saturday, 2 September 1995 13:50:30 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:14 UTC