- From: cowwoc <cowwoc@bbs.darktech.org>
- Date: Thu, 04 Jul 2013 09:44:32 -0400
- To: Julian Reschke <julian.reschke@gmx.de>
- CC: ietf-http-wg@w3.org
On 04/07/2013 5:36 AM, Julian Reschke wrote:
> On 2013-07-03 21:16, cowwoc wrote:
>> Hi,
>>
>> Now that status code 303 and others no longer imply GET, we need to
> > ...
>
> How so?
>
> 303 always implied GET. 301, 302, and 307 never implied GET.
>
> The only change we made is to allow 301 and 302 to rewrite POST to GET
> (because that's what UAs do).
>
> Best regards, Julian
>
I think you misunderstood what I meant. In HTTP 2.0, the following
sentence was added to the description of HTTP 303: "This status code is
applicable to any HTTP method."
Meaning, although it was originally meant to be returned in
response to HTTP POST, it is now legal to return from HTTP
GET/PUT/DELETE as well. At least, that is my interpretation.
Gili
Received on Thursday, 4 July 2013 13:45:25 UTC