- From: Pat Hayes <phayes@ihmc.us>
- Date: Thu, 9 Jul 2009 14:26:45 -0500
- To: "Roy T. Fielding" <fielding@gbiv.com>
- Cc: Jonathan Rees <jar@creativecommons.org>, Julian Reschke <julian.reschke@gmx.de>, HTTP Working Group <ietf-http-wg@w3.org>, www-tag@w3.org
On Jul 9, 2009, at 12:01 PM, Roy T. Fielding wrote: > On Jul 9, 2009, at 9:04 AM, Pat Hayes wrote: >> Hmm, then I am puzzled. Does 303 redirection really imply that the >> server **does not have** a transferable representation? Surely 303 >> redirection is used under other circumstances than this, >> circumstances which have nothing whatever to do with http-range-14 >> and were being used before the http-range-14 issue was even raised? >> No? > > No, at least not for GET requests. 303 (See Other) was originally > defined as "redirect with a different method" and not fully specified. > When HTTP was standardized, 303 became "see other" for the specific > purpose of redirecting a non-GET request to a GET of another resource. > Defining a specific purpose for 303 in response to a GET is what we > are doing right now. There was no pre-existing usage of 303 in > response > to a GET prior to the HTTPrange issue being decided. OK, thanks for the explanation. I had not realized that previous uses of 303 were restricted to non-GET requests. I guess this narrows the 'meaning' of a 303 response even more tightly than I thought. Pat > > ....Roy > > > > ------------------------------------------------------------ IHMC (850)434 8903 or (650)494 3973 40 South Alcaniz St. (850)202 4416 office Pensacola (850)202 4440 fax FL 32502 (850)291 0667 mobile phayesAT-SIGNihmc.us http://www.ihmc.us/users/phayes
Received on Thursday, 9 July 2009 19:27:32 UTC