Changeset 2502


Ignore:
Timestamp:
04/12/13 11:17:28 (6 years ago)
Author:
julian.reschke@…
Message:

s/filesystem/file system/ (see #234)

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

Legend:

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

    r2501 r2502  
    448448  }
    449449  @bottom-center {
    450        content: "Expires June 4, 2014";
     450       content: "Expires June 7, 2014";
    451451  }
    452452  @bottom-right {
     
    493493      <meta name="dct.creator" content="Reschke, J. F.">
    494494      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    495       <meta name="dct.issued" scheme="ISO8601" content="2013-12-01">
     495      <meta name="dct.issued" scheme="ISO8601" content="2013-12-04">
    496496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    497497      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines the semantics of HTTP/1.1 messages, as expressed by request methods, request header fields, response status codes, and response header fields, along with the payload of messages (metadata and body content) and mechanisms for content negotiation.">
     
    521521            <tr>
    522522               <td class="left">Intended status: Standards Track</td>
    523                <td class="right">December 1, 2013</td>
     523               <td class="right">December 4, 2013</td>
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: June 4, 2014</td>
     526               <td class="left">Expires: June 7, 2014</td>
    527527               <td class="right"></td>
    528528            </tr>
     
    553553            in progress”.
    554554         </p>
    555          <p>This Internet-Draft will expire on June 4, 2014.</p>
     555         <p>This Internet-Draft will expire on June 7, 2014.</p>
    556556      </div>
    557557      <div id="rfc.copyrightnotice">
     
    14691469                  people speak of retrieving some identifiable information via HTTP, they are generally referring to making a GET request.
    14701470               </p>
    1471                <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
     1471               <p id="rfc.section.4.3.1.p.2">It is tempting to think of resource identifiers as remote file system pathnames, and of representations as being a copy of
    14721472                  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
    14731473                  is just as likely to be implemented as a tree of content objects, a programmatic view on various database records, or a gateway
    1474                   to other information systems. Even when the URI mapping mechanism is tied to a filesystem, an origin server might be configured
     1474                  to other information systems. Even when the URI mapping mechanism is tied to a file system, an origin server might be configured
    14751475                  to execute the files with the request as input and send the output as the representation, rather than transfer the files directly.
    14761476                  Regardless, only the origin server needs to know how each of its resource identifiers corresponds to an implementation, and
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2501 r2502  
    12981298</t>
    12991299<t>
    1300    It is tempting to think of resource identifiers as remote filesystem
     1300   It is tempting to think of resource identifiers as remote file system
    13011301   pathnames, and of representations as being a copy of the contents of such
    13021302   files. In fact, that is how many resources are implemented (see
     
    13061306   objects, a programmatic view on various database records, or a gateway to
    13071307   other information systems. Even when the URI mapping mechanism is tied to a
    1308    filesystem, an origin server might be configured to execute the files with
     1308   file system, an origin server might be configured to execute the files with
    13091309   the request as input and send the output as the representation, rather than
    13101310   transfer the files directly. Regardless, only the origin server needs to
  • draft-ietf-httpbis/latest/p4-conditional.html

    r2501 r2502  
    448448  }
    449449  @bottom-center {
    450        content: "Expires June 4, 2014";
     450       content: "Expires June 7, 2014";
    451451  }
    452452  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2013-12-01">
     493      <meta name="dct.issued" scheme="ISO8601" content="2013-12-04">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    495495      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines HTTP/1.1 conditional requests, including metadata header fields for indicating state changes, request header fields for making preconditions on such state, and rules for constructing the responses to a conditional request when one or more preconditions evaluate to false.">
     
    517517            </tr>
    518518            <tr>
    519                <td class="left">Expires: June 4, 2014</td>
    520                <td class="right">December 1, 2013</td>
     519               <td class="left">Expires: June 7, 2014</td>
     520               <td class="right">December 4, 2013</td>
    521521            </tr>
    522522         </tbody>
     
    546546            in progress”.
    547547         </p>
    548          <p>This Internet-Draft will expire on June 4, 2014.</p>
     548         <p>This Internet-Draft will expire on June 7, 2014.</p>
    549549      </div>
    550550      <div id="rfc.copyrightnotice">
     
    826826               <p id="rfc.section.2.3.1.p.2">For example, a resource that has implementation-specific versioning applied to all changes might use an internal revision
    827827                  number, perhaps combined with a variance identifier for content negotiation, to accurately differentiate between representations.
    828                   Other implementations might use a collision-resistant hash of representation content, a combination of various filesystem
     828                  Other implementations might use a collision-resistant hash of representation content, a combination of various files system
    829829                  attributes, or a modification timestamp that has sub-second resolution.
    830830               </p>
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r2501 r2502  
    477477   accurately differentiate between representations.
    478478   Other implementations might use a collision-resistant hash of
    479    representation content,
    480    a combination of various filesystem attributes, or a modification
    481    timestamp that has sub-second resolution.
     479   representation content, a combination of various files system attributes, or
     480   a modification timestamp that has sub-second resolution.
    482481</t>
    483482<t>
Note: See TracChangeset for help on using the changeset viewer.