W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2011

Re: #310, was: #160: Redirects and non-GET methods

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 31 Aug 2011 10:54:12 +0200
Message-ID: <4E5DF6B4.8070606@gmx.de>
To: Mark Nottingham <mnot@mnot.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>
On 2011-08-08 10:10, Julian Reschke wrote:
> On 2011-08-08 09:25, Mark Nottingham wrote:
>> Yes; please go ahead and open one.
>> ...
>
> -> <http://trac.tools.ietf.org/wg/httpbis/trac/ticket/310>

Roy came up with a new intro for 303:

    The 303 status code indicates that the server is redirecting the
    user agent to a different resource, as indicated by a URI in the
    Location header field, that is intended to provide an indirect
    response to the original request.  In order to satisfy the original
    request, a user agent SHOULD perform a retrieval request using the
    Location URI, which may itself be redirected further, and present
    the eventual result as an answer to the original request.
    Note that the new URI in the Location header field is not considered
    equivalent to the effective request URI.

...which as a side effect avoids the explicit mention of GET; so I think 
we can close #310.

See <http://trac.tools.ietf.org/wg/httpbis/trac/changeset/1421>.

Best regards, Julian
Received on Wednesday, 31 August 2011 08:55:00 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:47 GMT