- From: Roy T. Fielding <fielding@gbiv.com>
- Date: Thu, 13 Sep 2007 08:28:48 -0700
- To: Rhys Lewis <rhys@volantis.com>
- Cc: "'Stuart Williams'" <skw@hp.com>, "'Ed Davies'" <edavies@nildram.co.uk>, "'Technical Architecture Group WG'" <www-tag@w3.org>
On Sep 12, 2007, at 12:25 AM, Rhys Lewis wrote: > Ok, that's a good point. What it actually says is > > "The response to the request can be found under a different URI and > SHOULD > be retrieved using a GET method on that resource." > > My interpretation is that when you get a 303 you don't get a > response to > the request you made. Otherwise, there would be no point in > redirecting. I > perhaps stated this a little strongly, but I believe that what I > wrote is > in the spirit of the intent of 303. You get a response to the request you made. It may not be the response that some applications of HTTP will be looking for, ultimately, but that is outside the scope of HTTP. Anyway, this is dancing around the point. It is false to say that a 303 response implies that the URI identifies a resource that is not an information resource. All it implies is what the 303 says -- if you want information about this resource in the form of a representation, then look over there. We don't need to speculate any further about the resource that has not been represented. ....Roy
Received on Thursday, 13 September 2007 15:29:02 UTC