* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 1683


Ignore:
Timestamp:
2012-06-21 05:52:32 (2 years ago)
Author:
julian.reschke@gmx.de
Message:

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

Location:
draft-ietf-httpbis/latest
Files:
2 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> 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r1682 r1683  
    13781378  <iref primary="true" item="Status Codes" subitem="201 Created" x:for-anchor=""/> 
    13791379<t> 
    1380    The request has been fulfilled and has resulted in a new resource being 
    1381    created.  
    1382 </t> 
    1383 <t> 
    1384    The newly created resource is typically linked to from the response payload, 
     1380   The request has been fulfilled and has resulted in one or more new resources 
     1381   being created.  
     1382</t> 
     1383<t> 
     1384   Newly created resources are typically linked to from the response payload, 
    13851385   with the most relevant URI also being carried in the Location header field. 
    13861386   If the newly created resource's URI is the same as the Effective Request URI, 
     
    13891389</t> 
    13901390<t> 
    1391    The origin server &MUST; create the resource before returning the 201 status 
     1391   The origin server &MUST; create the resource(s) before returning the 201 status 
    13921392   code. If the action cannot be carried out immediately, the server &SHOULD; 
    13931393   respond with 202 (Accepted) response instead. 
     
    13961396   A 201 response &MAY; contain an ETag response header field indicating 
    13971397   the current value of the entity-tag for the representation of the resource 
    1398    just created (see &header-etag;). 
     1398   identified by the Location header field or, in case the Location header 
     1399   field was omitted, by the Effective Request URI (see &header-etag;). 
    13991400</t> 
    14001401</section> 
     
    67776778      "ABNF requirements for recipients" 
    67786779    </t> 
     6780    <t> 
     6781      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/347"/>: 
     6782      "clarify that 201 can imply *multiple* resources were created" 
     6783    </t> 
    67796784  </list> 
    67806785</t> 
Note: See TracChangeset for help on using the changeset viewer.