Changeset 2162


Ignore:
Timestamp:
Jan 25, 2013, 5:00:05 AM (7 years ago)
Author:
fielding@…
Message:

(editorial) rewrite the oldest (and most awkward) sentence remaining from the original HTTP spec of 1993

Location:
draft-ietf-httpbis/latest
Files:
2 edited

Legend:

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

    r2161 r2162  
    13801380      <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>
    13811381      <div id="rfc.iref.g.16"></div>
    1382       <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of the selected representation for 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
     1382      <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of a current selected representation for 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
    13831383         people speak of retrieving some identifiable information via HTTP, they are generally referring to making a GET request.
    13841384      </p>
    1385       <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
    1386          of the process, unless that text happens to be the output of the process.
     1385      <p id="rfc.section.4.3.1.p.2">It is tempting to think of resource identifiers as remote filesystem pathnames, and of representations as being a copy of
     1386         the contents of such files. In fact, that is how many resources are implemented (see <a href="#attack.pathname" title="Attacks Based On File and Path Names">Section&nbsp;9.1</a> for related security considerations). However, there are no such limitations in practice. The HTTP interface for a resource
     1387         is just as likely to be implemented as a tree of content objects, a programmatic view on various database records, or a gateway
     1388         to other information systems. Even when the URI mapping mechanism is tied to a filesystem, an origin server might be configured
     1389         to execute the files with the request as input and send the output as the representation, rather then transfer the files directly.
     1390         Regardless, only the origin server needs to know how each of its resource identifiers correspond to an implementation, and
     1391         how each implementation manages to select and send a current representation of the target resource in a response to GET.
    13871392      </p>
    13881393      <p id="rfc.section.4.3.1.p.3">A client can alter the semantics of GET to be a "range request", requesting transfer of only some part(s) of the selected
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2161 r2162  
    12511251  <iref primary="true" item="GET method" x:for-anchor=""/>
    12521252<t>
    1253    The GET method requests transfer of the selected representation for
     1253   The GET method requests transfer of a current selected representation for
    12541254   the <x:ref>target resource</x:ref>. GET is the primary mechanism of
    12551255   information retrieval and the focus of almost all performance
     
    12571257   information via HTTP, they are generally referring to making a GET request.
    12581258</t>
    1259 <t>   
    1260    If the target resource is a data-producing process, the produced data will
    1261    be sent as the representation, not the source text of the process,
    1262    unless that text happens to be the output of the process.
     1259<t>
     1260   It is tempting to think of resource identifiers as remote filesystem
     1261   pathnames, and of representations as being a copy of the contents of such
     1262   files. In fact, that is how many resources are implemented (see
     1263   <xref target="attack.pathname"/> for related security considerations).
     1264   However, there are no such limitations in practice. The HTTP interface for
     1265   a resource is just as likely to be implemented as a tree of content
     1266   objects, a programmatic view on various database records, or a gateway to
     1267   other information systems. Even when the URI mapping mechanism is tied to a
     1268   filesystem, an origin server might be configured to execute the files with
     1269   the request as input and send the output as the representation, rather then
     1270   transfer the files directly. Regardless, only the origin server needs to
     1271   know how each of its resource identifiers correspond to an implementation,
     1272   and how each implementation manages to select and send a current
     1273   representation of the target resource in a response to GET.
    12631274</t>
    12641275<t>
Note: See TracChangeset for help on using the changeset viewer.