Changeset 758 for draft-ietf-httpbis/latest
- Timestamp:
- 08/02/10 16:19:43 (12 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 2 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r757 r758 910 910 <p id="rfc.section.6.1.p.2">An HTTP request representation, when present, is always associated with an anonymous (i.e., unidentified) resource.</p> 911 911 <p id="rfc.section.6.1.p.3">In the common case, an HTTP response is a representation of the resource located at the request-URI. However, this is not 912 always the case. To determine the URI of the resource a response is associated with, the following rules are used ( first match913 winning):912 always the case. To determine the URI of the resource a response is associated with, the following rules are used (with the 913 first applicable one being selected): 914 914 </p> 915 915 <ol> … … 1152 1152 <div id="rfc.iref.s.5"></div> 1153 1153 <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a> <a id="status.201" href="#status.201">201 Created</a></h3> 1154 <p id="rfc.section.8.2.2.p.1">The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced1154 <p id="rfc.section.8.2.2.p.1">The request has been fulfilled and has resulted in a new resource being created. The newly created resource can be referenced 1155 1155 by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header 1156 1156 field. The response <em class="bcp14">SHOULD</em> include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose -
draft-ietf-httpbis/latest/p2-semantics.xml
r757 r758 672 672 located at the request-URI. However, this is not always the case. To 673 673 determine the URI of the resource a response is associated with, the 674 following rules are used ( first match winning):674 following rules are used (with the first applicable one being selected): 675 675 </t> 676 676 <t><list style="numbers"> … … 1170 1170 <iref primary="true" item="Status Codes" subitem="201 Created" x:for-anchor=""/> 1171 1171 <t> 1172 The request has been fulfilled and resulted in a new resource being1172 The request has been fulfilled and has resulted in a new resource being 1173 1173 created. The newly created resource can be referenced by the URI(s) 1174 1174 returned in the entity of the response, with the most specific URI
Note: See TracChangeset
for help on using the changeset viewer.