Ignore:
Timestamp:
Feb 8, 2010, 8:19:43 AM (10 years ago)
Author:
julian.reschke@…
Message:

lang/grammar

File:
1 edited

Legend:

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

    r757 r758  
    910910      <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>
    911911      <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 match
    913          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):
    914914      </p>
    915915      <ol>
     
    11521152      <div id="rfc.iref.s.5"></div>
    11531153      <h3 id="rfc.section.8.2.2"><a href="#rfc.section.8.2.2">8.2.2</a>&nbsp;<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 referenced
     1154      <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
    11551155         by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header
    11561156         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
Note: See TracChangeset for help on using the changeset viewer.