Changeset 1683
- Timestamp:
- 21/06/12 12:52:32 (10 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r1682 r1683 1703 1703 <div id="rfc.iref.s.6"></div> 1704 1704 <h3 id="rfc.section.4.4.2"><a href="#rfc.section.4.4.2">4.4.2</a> <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 resourcebeing 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 carried1707 inthe Location header field. If the newly created resource's URI is the same as the Effective Request URI, this information1705 <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 1708 1708 can be omitted (e.g., in the case of a response to a PUT request). 1709 1709 </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. 1711 1711 </p> 1712 1712 <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>). 1714 1714 </p> 1715 1715 <div id="rfc.iref.25"></div> … … 4734 4734 </li> 4735 4735 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/361">http://tools.ietf.org/wg/httpbis/trac/ticket/361</a>>: "ABNF requirements for recipients" 4736 </li> 4737 <li> <<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/347">http://tools.ietf.org/wg/httpbis/trac/ticket/347</a>>: "clarify that 201 can imply *multiple* resources were created" 4736 4738 </li> 4737 4739 </ul> -
draft-ietf-httpbis/latest/p2-semantics.xml
r1682 r1683 1378 1378 <iref primary="true" item="Status Codes" subitem="201 Created" x:for-anchor=""/> 1379 1379 <t> 1380 The request has been fulfilled and has resulted in a new resource being1381 created.1382 </t> 1383 <t> 1384 The newly created resource istypically 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, 1385 1385 with the most relevant URI also being carried in the Location header field. 1386 1386 If the newly created resource's URI is the same as the Effective Request URI, … … 1389 1389 </t> 1390 1390 <t> 1391 The origin server &MUST; create the resource before returning the 201 status1391 The origin server &MUST; create the resource(s) before returning the 201 status 1392 1392 code. If the action cannot be carried out immediately, the server &SHOULD; 1393 1393 respond with 202 (Accepted) response instead. … … 1396 1396 A 201 response &MAY; contain an ETag response header field indicating 1397 1397 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;). 1399 1400 </t> 1400 1401 </section> … … 6777 6778 "ABNF requirements for recipients" 6778 6779 </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> 6779 6784 </list> 6780 6785 </t>
Note: See TracChangeset
for help on using the changeset viewer.