[Zope3-dev] DISCUSS: Correct sequence for PUT
Paul Everitt
paul@zope-europe.org
Sun, 13 Apr 2003 16:54:51 +0200
You're right, I wasn't clear. It's only when the server tells the
client (with a 301 status) that the Location header must be used. (I
think, at least. The use of SHOULD in 10.3.2 muddies the water, I
think the SHOULD only applies to HEAD, but it is MUST when doing a PUT.)
Interestingly, Apache/mod_dav chooses to return a Location in the
response, even for 201 Created status codes. I think that was my
mistake, thinking that Apache/mod_dav behavior equated to the standard.
:^)
--Paul
On Thursday, Feb 27, 2003, at 14:59 Europe/Paris, Jim Fulton wrote:
> Paul Everitt wrote:
>
> ...
>
>> 2) I'm not sure Zope 3 is doing the PUT correctly. I did a PUT of a
>> new resource, and RFC 2616 (HTTP/1.1) Section 9.6 says that a status
>> code of 201 should be returned. Also, the server should return a
>> Location: header with the URI of the newly created resource.
>> Perhaps I'm reading 9.6 incorrectly?
>
> I don't see any mention of setting a Location header in section 9.6.
>
> I'm looking at RFC 2616, dated June 1999.
>
> Jim
>
> --
> Jim Fulton mailto:jim@zope.com Python Powered!
> CTO (888) 344-4332 http://www.python.org
> Zope Corporation http://www.zope.com http://www.zope.org
>
>