Ignore:
Timestamp:
Jan 5, 2013, 3:42:34 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) Clarify that GET means retrieval; addresses #315

File:
1 edited

Legend:

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

    r2087 r2088  
    13871387      <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a>&nbsp;<a id="GET" href="#GET">GET</a></h3>
    13881388      <div id="rfc.iref.g.16"></div>
    1389       <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of a current representation of the <a href="#resources" class="smpl">target resource</a>.
     1389      <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of a current representation of the <a href="#resources" class="smpl">target resource</a>. GET is the primary mechanism of information retrieval and the focus of almost all performance optimizations. Hence, when
     1390         people speak of retrieving some identifiable information via HTTP, they are generally referring to making a GET request.
    13901391      </p>
    13911392      <p id="rfc.section.4.3.1.p.2">If the target resource is a data-producing process, the produced data will be sent as the representation, not the source text
     
    15661567      <p id="rfc.section.4.3.7.p.1">The OPTIONS method requests information about the communication options available on the request/response chain identified
    15671568         by the effective request URI. This method allows a client to determine the options and/or requirements associated with a resource,
    1568          or the capabilities of a server, without implying a resource action or initiating a resource retrieval.
     1569         or the capabilities of a server, without implying a resource action.
    15691570      </p>
    15701571      <p id="rfc.section.4.3.7.p.2">Responses to the OPTIONS method are not cacheable.</p>
Note: See TracChangeset for help on using the changeset viewer.