Ticket #331: 331.2.diff

File 331.2.diff, 1.7 KB (added by julian.reschke@…, 10 years ago)

Proposed patch

  • p2-semantics.xml

     
    15051505  <iref primary="true" item="Status Codes" subitem="201 Created" x:for-anchor=""/>
    15061506<t>
    15071507   The request has been fulfilled and has resulted in a new resource being
    1508    created. The newly created resource can be referenced by the URI(s)
    1509    returned in the payload of the response, with the most specific URI
    1510    for the resource given by a Location header field. The response
    1511    can include a payload containing a list of resource
    1512    characteristics and location(s) from which the user or user agent can
    1513    choose the one most appropriate.
     1508   created.
    15141509</t>
    15151510<t>
     1511   The newly created resource is typically linked to from the response payload,
     1512   with the most relevant URI also being carried in the Location header field.
     1513   If the newly created resource's URI is the same as the Effective Request URI,
     1514   this information can be omitted (e.g., in the case of a response to a PUT
     1515   request). 
     1516</t>
     1517<t>
    15161518   The origin server &MUST; create the resource before returning the 201 status
    15171519   code. If the action cannot be carried out immediately, the server &SHOULD;
    15181520   respond with 202 (Accepted) response instead.
     
    47064708      "Misplaced text on connection handling in p2"
    47074709    </t>
    47084710    <t>
     4711      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/331"/>:
     4712      "clarify that 201 doesn't require Location header fields"
     4713    </t>
     4714    <t>
    47094715      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/332"/>:
    47104716      "relax requirements on hypertext in 3/4/5xx error responses"
    47114717    </t>