Changeset 2162 for draft-ietf-httpbis/latest/p2-semantics.html
- Timestamp:
- 25/01/13 13:00:05 (8 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p2-semantics.html
r2161 r2162 1380 1380 <h3 id="rfc.section.4.3.1"><a href="#rfc.section.4.3.1">4.3.1</a> <a id="GET" href="#GET">GET</a></h3> 1381 1381 <div id="rfc.iref.g.16"></div> 1382 <p id="rfc.section.4.3.1.p.1">The GET method requests transfer of theselected 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, when1382 <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 1383 1383 people speak of retrieving some identifiable information via HTTP, they are generally referring to making a GET request. 1384 1384 </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 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. 1387 1392 </p> 1388 1393 <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
Note: See TracChangeset
for help on using the changeset viewer.