Ticket #331: 331.2.diff

p2-semantics.xml

@@ -1505 +1505 @@
   <iref primary="true" item="Status Codes" subitem="201 Created" x:for-anchor=""/>
 <t>
    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. 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.
+   created. 
 </t>
 <t>
+   The newly created resource is typically linked to from the response payload,
+   with the most relevant URI also being carried in the Location header field.
+   If the newly created resource's URI is the same as the Effective Request URI,
+   this information can be omitted (e.g., in the case of a response to a PUT
+   request).  
+</t>
+<t>
    The origin server &MUST; create the resource before returning the 201 status
    code. If the action cannot be carried out immediately, the server &SHOULD;
    respond with 202 (Accepted) response instead.
@@ -4706 +4708 @@
       "Misplaced text on connection handling in p2"
     </t>
     <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/331"/>:
+      "clarify that 201 doesn't require Location header fields"
+    </t>
+    <t>
       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/332"/>:
       "relax requirements on hypertext in 3/4/5xx error responses"
     </t>