Changeset 2053


Ignore:
Timestamp:
Dec 16, 2012, 4:26:52 PM (7 years ago)
Author:
fielding@…
Message:

oops, fix a few phrasing of return vs send due to last commit

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p1-messaging.html

    r2052 r2053  
    449449  }
    450450  @bottom-center {
    451        content: "Expires June 18, 2013";
     451       content: "Expires June 19, 2013";
    452452  }
    453453  @bottom-right {
     
    491491      <meta name="dct.creator" content="Reschke, J. F.">
    492492      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest">
    493       <meta name="dct.issued" scheme="ISO8601" content="2012-12-15">
     493      <meta name="dct.issued" scheme="ISO8601" content="2012-12-16">
    494494      <meta name="dct.replaces" content="urn:ietf:rfc:2145">
    495495      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
     
    520520            <tr>
    521521               <td class="left">Intended status: Standards Track</td>
    522                <td class="right">December 15, 2012</td>
     522               <td class="right">December 16, 2012</td>
    523523            </tr>
    524524            <tr>
    525                <td class="left">Expires: June 18, 2013</td>
     525               <td class="left">Expires: June 19, 2013</td>
    526526               <td class="right"></td>
    527527            </tr>
     
    551551         in progress”.
    552552      </p>
    553       <p>This Internet-Draft will expire on June 18, 2013.</p>
     553      <p>This Internet-Draft will expire on June 19, 2013.</p>
    554554      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    555555      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    24792479      </p>
    24802480      <h2 id="rfc.section.8.3"><a href="#rfc.section.8.3">8.3</a>&nbsp;<a id="attack.pathname" href="#attack.pathname">Attacks Based On File and Path Names</a></h2>
    2481       <p id="rfc.section.8.3.p.1">Origin servers <em class="bcp14">SHOULD</em> be careful to restrict the documents sent by HTTP requests to be only those that were intended by the server administrators.
     2481      <p id="rfc.section.8.3.p.1">Origin servers <em class="bcp14">SHOULD</em> be careful to restrict the documents sent in response to HTTP requests to be only those that were intended by the server administrators.
    24822482         If an HTTP server translates HTTP URIs directly into file system calls, the server <em class="bcp14">MUST</em> take special care not to serve files that were not intended to be delivered to HTTP clients. For example, UNIX, Microsoft
    24832483         Windows, and other operating systems use ".." as a path component to indicate a directory level above the current one. On
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r2052 r2053  
    35383538<t>
    35393539   Origin servers &SHOULD; be careful to restrict
    3540    the documents sent by HTTP requests to be only those that were
     3540   the documents sent in response to HTTP requests to be only those that were
    35413541   intended by the server administrators. If an HTTP server translates
    35423542   HTTP URIs directly into file system calls, the server &MUST; take
  • draft-ietf-httpbis/latest/p5-range.html

    r2052 r2053  
    449449  }
    450450  @bottom-center {
    451        content: "Expires June 18, 2013";
     451       content: "Expires June 19, 2013";
    452452  }
    453453  @bottom-right {
     
    493493      <meta name="dct.creator" content="Reschke, J. F.">
    494494      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest">
    495       <meta name="dct.issued" scheme="ISO8601" content="2012-12-15">
     495      <meta name="dct.issued" scheme="ISO8601" content="2012-12-16">
    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 range requests and the rules for constructing and combining responses to those requests.">
     
    519519            </tr>
    520520            <tr>
    521                <td class="left">Expires: June 18, 2013</td>
     521               <td class="left">Expires: June 19, 2013</td>
    522522               <td class="right">J. Reschke, Editor</td>
    523523            </tr>
     
    528528            <tr>
    529529               <td class="left"></td>
    530                <td class="right">December 15, 2012</td>
     530               <td class="right">December 16, 2012</td>
    531531            </tr>
    532532         </tbody>
     
    553553         in progress”.
    554554      </p>
    555       <p>This Internet-Draft will expire on June 18, 2013.</p>
     555      <p>This Internet-Draft will expire on June 19, 2013.</p>
    556556      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    557557      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    703703         length of the selected resource.)
    704704      </p>
    705       <p id="rfc.section.3.2.p.2">When this status code is sent for a byte-range request, the response <em class="bcp14">SHOULD</em> include a <a href="#header.content-range" class="smpl">Content-Range</a> header field specifying the current length of the representation (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges content-type.
     705      <p id="rfc.section.3.2.p.2">When this status code is sent in response to a byte-range request, the response <em class="bcp14">SHOULD</em> include a <a href="#header.content-range" class="smpl">Content-Range</a> header field specifying the current length of the representation (see <a href="#header.content-range" id="rfc.xref.header.content-range.3" title="Content-Range">Section&nbsp;5.2</a>). This response <em class="bcp14">MUST NOT</em> use the multipart/byteranges media type.
    706706      </p>
    707707      <div id="rfc.figure.u.2"></div>
     
    12331233      <p id="rfc.section.B.p.2">The Content-Range header field only has meaning when the status code explicitly defines its use. (<a href="#header.content-range" id="rfc.xref.header.content-range.5" title="Content-Range">Section&nbsp;5.2</a>)
    12341234      </p>
    1235       <p id="rfc.section.B.p.3">Servers are given more leeway in what they send to a range request, in order to mitigate malicious (or just greedy) clients.</p>
     1235      <p id="rfc.section.B.p.3">Servers are given more leeway in how they respond to a range request, in order to mitigate abuse by malicious (or just greedy)
     1236         clients.
     1237      </p>
    12361238      <p id="rfc.section.B.p.4">multipart/byteranges can consist of a single part. (<a href="#internet.media.type.multipart.byteranges" title="Internet Media Type multipart/byteranges">Appendix&nbsp;A</a>)
    12371239      </p>
  • draft-ietf-httpbis/latest/p5-range.xml

    r2052 r2053  
    296296</t>
    297297<t>
    298    When this status code is sent for a byte-range request, the
     298   When this status code is sent in response to a byte-range request, the
    299299   response &SHOULD; include a <x:ref>Content-Range</x:ref> header field
    300300   specifying the current length of the representation (see <xref target="header.content-range"/>).
    301    This response &MUST-NOT; use the multipart/byteranges content-type.
     301   This response &MUST-NOT; use the multipart/byteranges media type.
    302302</t>
    303303<figure>
     
    13071307</t>
    13081308<t>
    1309   Servers are given more leeway in what they send to a range request,
    1310   in order to mitigate malicious (or just greedy) clients.
     1309  Servers are given more leeway in how they respond to a range request,
     1310  in order to mitigate abuse by malicious (or just greedy) clients.
    13111311</t>
    13121312<t>
  • draft-ietf-httpbis/latest/p6-cache.html

    r2052 r2053  
    452452  }
    453453  @bottom-center {
    454        content: "Expires June 18, 2013";
     454       content: "Expires June 19, 2013";
    455455  }
    456456  @bottom-right {
     
    498498      <meta name="dct.creator" content="Reschke, J. F.">
    499499      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    500       <meta name="dct.issued" scheme="ISO8601" content="2012-12-15">
     500      <meta name="dct.issued" scheme="ISO8601" content="2012-12-16">
    501501      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    502502      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: June 18, 2013</td>
     526               <td class="left">Expires: June 19, 2013</td>
    527527               <td class="right">J. Reschke, Editor</td>
    528528            </tr>
     
    533533            <tr>
    534534               <td class="left"></td>
    535                <td class="right">December 15, 2012</td>
     535               <td class="right">December 16, 2012</td>
    536536            </tr>
    537537         </tbody>
     
    559559         in progress”.
    560560      </p>
    561       <p>This Internet-Draft will expire on June 18, 2013.</p>
     561      <p>This Internet-Draft will expire on June 19, 2013.</p>
    562562      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    563563      <p>Copyright © 2012 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    727727      </p>
    728728      <ul class="empty">
    729          <li>The time at which the origin server intends that a representation no longer be sent by a cache without further validation.</li>
     729         <li>The time at which the origin server intends that a representation no longer be used by a cache without further validation.</li>
    730730      </ul>
    731731      <p id="rfc.section.1.2.p.7"> <span id="rfc.iref.h.1"></span>  <dfn>heuristic expiration time</dfn> 
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2052 r2053  
    211211   <list>
    212212      <t>The time at which the origin server intends that a representation
    213       no longer be sent by a cache without further validation.</t>
     213      no longer be used by a cache without further validation.</t>
    214214   </list>
    215215</t>
Note: See TracChangeset for help on using the changeset viewer.