Changeset 1683

Timestamp:

Jun 21, 2012, 5:52:32 AM (7 years ago)

Author:

julian.reschke@…

Message:

Clarify that status 201 can mean that multiple resources have been created (see #347)

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (2 diffs)
• p2-semantics.xml (modified) (4 diffs)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -1703 +1703 @@
       <div id="rfc.iref.s.6"></div>
       <h3 id="rfc.section.4.4.2"><a href="#rfc.section.4.4.2">4.4.2</a>&nbsp;<a id="status.201" href="#status.201">201 Created</a></h3>
-      <p id="rfc.section.4.4.2.p.1">The request has been fulfilled and has resulted in a new resource being created.</p>
-      <p id="rfc.section.4.4.2.p.2">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
+      <p id="rfc.section.4.4.2.p.1">The request has been fulfilled and has resulted in one or more new resources being created.</p>
+      <p id="rfc.section.4.4.2.p.2">Newly created resources are 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).
       </p>
-      <p id="rfc.section.4.4.2.p.3">The origin server <em class="bcp14">MUST</em> create the resource before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with 202 (Accepted) response instead.
+      <p id="rfc.section.4.4.2.p.3">The origin server <em class="bcp14">MUST</em> create the resource(s) before returning the 201 status code. If the action cannot be carried out immediately, the server <em class="bcp14">SHOULD</em> respond with 202 (Accepted) response instead.
       </p>
       <p id="rfc.section.4.4.2.p.4">A 201 response <em class="bcp14">MAY</em> contain an ETag response header field indicating the current value of the entity-tag for the representation of the resource
-         just created (see <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
+         identified by the Location header field or, in case the Location header field was omitted, by the Effective Request URI (see <a href="p4-conditional.html#header.etag" title="ETag">Section 2.3</a> of <a href="#Part4" id="rfc.xref.Part4.9"><cite title="HTTP/1.1, part 4: Conditional Requests">[Part4]</cite></a>).
       </p>
       <div id="rfc.iref.25"></div>
@@ -4734 +4734 @@
          </li>
          <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>&gt;: "ABNF requirements for recipients"
+         </li>
+         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/347">http://tools.ietf.org/wg/httpbis/trac/ticket/347</a>&gt;: "clarify that 201 can imply *multiple* resources were created"
          </li>
       </ul>

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -1378 +1378 @@
   <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. 
-</t>
-<t>
-   The newly created resource is typically linked to from the response payload,
+   The request has been fulfilled and has resulted in one or more new resources
+   being created. 
+</t>
+<t>
+   Newly created resources are 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,
@@ -1389 +1389 @@
 </t>
 <t>
-   The origin server &MUST; create the resource before returning the 201 status
+   The origin server &MUST; create the resource(s) before returning the 201 status
    code. If the action cannot be carried out immediately, the server &SHOULD;
    respond with 202 (Accepted) response instead.
@@ -1396 +1396 @@
    A 201 response &MAY; contain an ETag response header field indicating
    the current value of the entity-tag for the representation of the resource
-   just created (see &header-etag;).
+   identified by the Location header field or, in case the Location header
+   field was omitted, by the Effective Request URI (see &header-etag;).
 </t>
 </section>
@@ -6777 +6778 @@
       "ABNF requirements for recipients"
     </t>
+    <t>
+      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/347"/>:
+      "clarify that 201 can imply *multiple* resources were created"
+    </t>
   </list>
 </t>