Changeset 2196 for draft-ietf-httpbis

Timestamp:

03/03/13 14:29:49 (10 years ago)

Author:

julian.reschke@…

Message:

fix typos

Location:

draft-ietf-httpbis/latest

Files:

• p2-semantics.html (modified) (6 diffs)
• p2-semantics.xml (modified) (2 diffs)
• p5-range.html (modified) (6 diffs)
• p5-range.xml (modified) (1 diff)

draft-ietf-httpbis/latest/p2-semantics.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires September 2, 2013"; 
+       content: "Expires September 4, 2013"; 
   } 
   @bottom-right {
@@ -494 +494 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-03-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-03-03">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -522 +522 @@
             <tr>
                <td class="left">Intended status: Standards Track</td>
-               <td class="right">March 1, 2013</td>
+               <td class="right">March 3, 2013</td>
             </tr>
             <tr>
-               <td class="left">Expires: September 2, 2013</td>
+               <td class="left">Expires: September 4, 2013</td>
                <td class="right"></td>
             </tr>
@@ -553 +553 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on September 2, 2013.</p>
+      <p>This Internet-Draft will expire on September 4, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -3321 +3321 @@
          if the response they occur in has explicit freshness information; however, status codes that are defined as being cacheable
          are allowed to be cached without explicit freshness information. Likewise, the definition of a status code can place constraints
-         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.
+         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.
       </p>
       <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
@@ -3855 +3855 @@
       <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>
       <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
-         representations. Implementors need to be aware that most file systems are not designed to protect against malicious file or
+         representations. Implementers need to be aware that most file systems are not designed to protect against malicious file or
          path names, and thus depend on the origin server to avoid mapping to file names, folders, or directories that have special
          significance to the system.

draft-ietf-httpbis/latest/p2-semantics.xml

@@ -4342 +4342 @@
    defined as being cacheable are allowed to be cached without explicit
    freshness information. Likewise, the definition of a status code can place
-   constraints upon cache behaviour. See &caching; for more information.
+   constraints upon cache behavior. See &caching; for more information.
 </t>
 <t>   
@@ -4872 +4872 @@
    Origin servers frequently make use of their local file system to manage the
    mapping from effective request URI to resource representations.
-   Implementors need to be aware that most file systems are not designed to
+   Implementers need to be aware that most file systems are not designed to
    protect against malicious file or path names, and thus depend on the
    origin server to avoid mapping to file names, folders, or directories that

draft-ietf-httpbis/latest/p5-range.html

@@ -449 +449 @@
   } 
   @bottom-center {
-       content: "Expires September 2, 2013"; 
+       content: "Expires September 4, 2013"; 
   } 
   @bottom-right {
@@ -492 +492 @@
       <meta name="dct.creator" content="Reschke, J. F.">
       <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
-      <meta name="dct.issued" scheme="ISO8601" content="2013-03-01">
+      <meta name="dct.issued" scheme="ISO8601" content="2013-03-03">
       <meta name="dct.replaces" content="urn:ietf:rfc:2616">
       <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.">
@@ -518 +518 @@
             </tr>
             <tr>
-               <td class="left">Expires: September 2, 2013</td>
+               <td class="left">Expires: September 4, 2013</td>
                <td class="right">J. Reschke, Editor</td>
             </tr>
@@ -527 +527 @@
             <tr>
                <td class="left"></td>
-               <td class="right">March 1, 2013</td>
+               <td class="right">March 3, 2013</td>
             </tr>
          </tbody>
@@ -552 +552 @@
          in progress”.
       </p>
-      <p>This Internet-Draft will expire on September 2, 2013.</p>
+      <p>This Internet-Draft will expire on September 4, 2013.</p>
       <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
       <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
@@ -791 +791 @@
       <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>
       <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
-         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>).
+         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>).
       </p>
       <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

@@ -508 +508 @@
    server is successfully fulfilling a range request for the target resource
    by transferring one or more parts of the selected representation that
-   correspond to the satisfiable ranges found in the requests's
+   correspond to the satisfiable ranges found in the request's
    <x:ref>Range</x:ref> header field (<xref target="header.range"/>).
 </t>