Ignore:
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)

File:
1 edited

Legend:

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

    r1682 r1683  
    17031703      <div id="rfc.iref.s.6"></div>
    17041704      <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>
    1705       <p id="rfc.section.4.4.2.p.1">The request has been fulfilled and has resulted in a new resource being created.</p>
    1706       <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
    1707          in the Location header field. If the newly created resource's URI is the same as the Effective Request URI, this information
     1705      <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>
     1706      <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
     1707         the Location header field. If the newly created resource's URI is the same as the Effective Request URI, this information
    17081708         can be omitted (e.g., in the case of a response to a PUT request).
    17091709      </p>
    1710       <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.
     1710      <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.
    17111711      </p>
    17121712      <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
    1713          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>).
     1713         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>).
    17141714      </p>
    17151715      <div id="rfc.iref.25"></div>
     
    47344734         </li>
    47354735         <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"
     4736         </li>
     4737         <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"
    47364738         </li>
    47374739      </ul>
Note: See TracChangeset for help on using the changeset viewer.