Ignore:
Timestamp:
Mar 10, 2012, 4:29:29 AM (7 years ago)
Author:
julian.reschke@…
Message:

clarify that 201 doesn't require Location header fields (see #331)

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1572 r1577  
    15081508<t>
    15091509   The request has been fulfilled and has resulted in a new resource being
    1510    created. The newly created resource can be referenced by the URI(s)
    1511    returned in the payload of the response, with the most specific URI
    1512    for the resource given by a Location header field. The response
    1513    can include a payload containing a list of resource
    1514    characteristics and location(s) from which the user or user agent can
    1515    choose the one most appropriate.
     1510   created.
     1511</t>
     1512<t>
     1513   The newly created resource is typically linked to from the response payload,
     1514   with the most relevant URI also being carried in the Location header field.
     1515   If the newly created resource's URI is the same as the Effective Request URI,
     1516   this information can be omitted (e.g., in the case of a response to a PUT
     1517   request). 
    15161518</t>
    15171519<t>
     
    47134715    </t>
    47144716    <t>
     4717      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/331"/>:
     4718      "clarify that 201 doesn't require Location header fields"
     4719    </t>
     4720    <t>
    47154721      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/332"/>:
    47164722      "relax requirements on hypertext in 3/4/5xx error responses"
Note: See TracChangeset for help on using the changeset viewer.