Changeset 2196


Ignore:
Timestamp:
Mar 3, 2013, 6:29:49 AM (6 years ago)
Author:
julian.reschke@…
Message:

fix typos

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

Legend:

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

    r2195 r2196  
    449449  }
    450450  @bottom-center {
    451        content: "Expires September 2, 2013";
     451       content: "Expires September 4, 2013";
    452452  }
    453453  @bottom-right {
     
    494494      <meta name="dct.creator" content="Reschke, J. F.">
    495495      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    496       <meta name="dct.issued" scheme="ISO8601" content="2013-03-01">
     496      <meta name="dct.issued" scheme="ISO8601" content="2013-03-03">
    497497      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    498498      <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.">
     
    522522            <tr>
    523523               <td class="left">Intended status: Standards Track</td>
    524                <td class="right">March 1, 2013</td>
     524               <td class="right">March 3, 2013</td>
    525525            </tr>
    526526            <tr>
    527                <td class="left">Expires: September 2, 2013</td>
     527               <td class="left">Expires: September 4, 2013</td>
    528528               <td class="right"></td>
    529529            </tr>
     
    553553         in progress”.
    554554      </p>
    555       <p>This Internet-Draft will expire on September 2, 2013.</p>
     555      <p>This Internet-Draft will expire on September 4, 2013.</p>
    556556      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    557557      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    33213321         if the response they occur in has explicit freshness information; however, status codes that are defined as being cacheable
    33223322         are allowed to be cached without explicit freshness information. Likewise, the definition of a status code can place constraints
    3323          upon cache behaviour. See <a href="#Part6" id="rfc.xref.Part6.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for more information.
     3323         upon cache behavior. See <a href="#Part6" id="rfc.xref.Part6.28"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a> for more information.
    33243324      </p>
    33253325      <p id="rfc.section.8.2.2.p.6">Finally, the definition of a new status code ought to indicate whether the payload has any implied association with an identified
     
    38553855      <h2 id="rfc.section.9.1"><a href="#rfc.section.9.1">9.1</a>&nbsp;<a id="attack.pathname" href="#attack.pathname">Attacks Based On File and Path Names</a></h2>
    38563856      <p id="rfc.section.9.1.p.1">Origin servers frequently make use of their local file system to manage the mapping from effective request URI to resource
    3857          representations. Implementors need to be aware that most file systems are not designed to protect against malicious file or
     3857         representations. Implementers need to be aware that most file systems are not designed to protect against malicious file or
    38583858         path names, and thus depend on the origin server to avoid mapping to file names, folders, or directories that have special
    38593859         significance to the system.
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2195 r2196  
    43424342   defined as being cacheable are allowed to be cached without explicit
    43434343   freshness information. Likewise, the definition of a status code can place
    4344    constraints upon cache behaviour. See &caching; for more information.
     4344   constraints upon cache behavior. See &caching; for more information.
    43454345</t>
    43464346<t>   
     
    48724872   Origin servers frequently make use of their local file system to manage the
    48734873   mapping from effective request URI to resource representations.
    4874    Implementors need to be aware that most file systems are not designed to
     4874   Implementers need to be aware that most file systems are not designed to
    48754875   protect against malicious file or path names, and thus depend on the
    48764876   origin server to avoid mapping to file names, folders, or directories that
  • draft-ietf-httpbis/latest/p5-range.html

    r2195 r2196  
    449449  }
    450450  @bottom-center {
    451        content: "Expires September 2, 2013";
     451       content: "Expires September 4, 2013";
    452452  }
    453453  @bottom-right {
     
    492492      <meta name="dct.creator" content="Reschke, J. F.">
    493493      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    494       <meta name="dct.issued" scheme="ISO8601" content="2013-03-01">
     494      <meta name="dct.issued" scheme="ISO8601" content="2013-03-03">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    496496      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines range requests and the rules for constructing and combining responses to those requests.">
     
    518518            </tr>
    519519            <tr>
    520                <td class="left">Expires: September 2, 2013</td>
     520               <td class="left">Expires: September 4, 2013</td>
    521521               <td class="right">J. Reschke, Editor</td>
    522522            </tr>
     
    527527            <tr>
    528528               <td class="left"></td>
    529                <td class="right">March 1, 2013</td>
     529               <td class="right">March 3, 2013</td>
    530530            </tr>
    531531         </tbody>
     
    552552         in progress”.
    553553      </p>
    554       <p>This Internet-Draft will expire on September 2, 2013.</p>
     554      <p>This Internet-Draft will expire on September 4, 2013.</p>
    555555      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    556556      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    791791      <h2 id="rfc.section.4.1"><a href="#rfc.section.4.1">4.1</a>&nbsp;<a id="status.206" href="#status.206">206 Partial Content</a></h2>
    792792      <p id="rfc.section.4.1.p.1">The <dfn>206 (Partial Content)</dfn> status code indicates that the server is successfully fulfilling a range request for the target resource by transferring one
    793          or more parts of the selected representation that correspond to the satisfiable ranges found in the requests's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;3.1</a>).
     793         or more parts of the selected representation that correspond to the satisfiable ranges found in the request's <a href="#header.range" class="smpl">Range</a> header field (<a href="#header.range" id="rfc.xref.header.range.2" title="Range">Section&nbsp;3.1</a>).
    794794      </p>
    795795      <p id="rfc.section.4.1.p.2">If a single part is being transferred, the server generating the 206 response <em class="bcp14">MUST</em> generate a <a href="#header.content-range" class="smpl">Content-Range</a> header field, describing what range of the selected representation is enclosed, and a payload consisting of the range. For
  • draft-ietf-httpbis/latest/p5-range.xml

    r2195 r2196  
    508508   server is successfully fulfilling a range request for the target resource
    509509   by transferring one or more parts of the selected representation that
    510    correspond to the satisfiable ranges found in the requests's
     510   correspond to the satisfiable ranges found in the request's
    511511   <x:ref>Range</x:ref> header field (<xref target="header.range"/>).
    512512</t>
Note: See TracChangeset for help on using the changeset viewer.