W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2012

#331: clarify that 201 doesn't require Location header fields

From: Julian Reschke <julian.reschke@gmx.de>
Date: Wed, 07 Mar 2012 14:27:15 +0100
Message-ID: <4F576233.8010101@gmx.de>
To: HTTP Working Group <ietf-http-wg@w3.org>
Hi there.

 From the bug:

> "The newly created resource can be referenced by the URI(s) returned in the payload of the response, with the most specific URI for the resource given by a Location header field."
>
> Some people read this as a requirement to include "Location". At least for PUT->201 that's nonsense, however.

Proposed change:

7.2.2.  201 Created

    The request has been fulfilled and has resulted in a new resource
    being created.  The newly created resource can be referenced by the
    URI(s) returned in the payload of the response, with the most
    specific URI for the resource given by a Location header field.  For
    a PUT request, the URI of the newly created resource is the effective
    request URI, and thus the response does not need to carry any
    additional information.

    The response can include a payload containing a list of resource
    characteristics and location(s) from which the user or user agent can
    choose the one most appropriate.

    (...)


(<http://trac.tools.ietf.org/wg/httpbis/trac/attachment/ticket/331/331.diff>)

Feedback appreciated, Julian
Received on Wednesday, 7 March 2012 13:27:50 GMT

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