* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Changeset 756


Ignore:
Timestamp:
2010-02-02 04:04:50 (5 years ago)
Author:
julian.reschke@gmx.de
Message:

editorial: consistently uppercase sentence starts after "Note:"

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

Legend:

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

    r754 r756  
    404404      <meta name="dct.creator" content="Reschke, J. F."> 
    405405      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p1-messaging-latest"> 
    406       <meta name="dct.issued" scheme="ISO8601" content="2010-02-01"> 
     406      <meta name="dct.issued" scheme="ISO8601" content="2010-02-02"> 
    407407      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    408408      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 1 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 1 provides an overview of HTTP and its associated terminology, defines the &#34;http&#34; and &#34;https&#34; Uniform Resource Identifier (URI) schemes, defines the generic message syntax and parsing requirements for HTTP message frames, and describes general security concerns for implementations."> 
     
    435435            </tr> 
    436436            <tr> 
    437                <td class="left">Expires: August 5, 2010</td> 
     437               <td class="left">Expires: August 6, 2010</td> 
    438438               <td class="right">HP</td> 
    439439            </tr> 
     
    488488            <tr> 
    489489               <td class="left"></td> 
    490                <td class="right">February 1, 2010</td> 
     490               <td class="right">February 2, 2010</td> 
    491491            </tr> 
    492492         </tbody> 
     
    520520      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 
    521521      </p> 
    522       <p>This Internet-Draft will expire in August 5, 2010.</p> 
     522      <p>This Internet-Draft will expire in August 6, 2010.</p> 
    523523      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    524524      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    11691169      </p> 
    11701170      <div class="note" id="rfc.section.3.2.p.7">  
    1171          <p> <b>Note:</b> the "Set-Cookie" header as implemented in practice (as opposed to how it is specified in <a href="#RFC2109" id="rfc.xref.RFC2109.1"><cite title="HTTP State Management Mechanism">[RFC2109]</cite></a>) can occur multiple times, but does not use the list syntax, and thus cannot be combined into a single line. (See Appendix 
     1171         <p> <b>Note:</b> The "Set-Cookie" header as implemented in practice (as opposed to how it is specified in <a href="#RFC2109" id="rfc.xref.RFC2109.1"><cite title="HTTP State Management Mechanism">[RFC2109]</cite></a>) can occur multiple times, but does not use the list syntax, and thus cannot be combined into a single line. (See Appendix 
    11721172            A.2.3 of <a href="#Kri2001" id="rfc.xref.Kri2001.1"><cite title="HTTP Cookies: Standards, Privacy, and Politics">[Kri2001]</cite></a> for details.) Also note that the Set-Cookie2 header specified in <a href="#RFC2965" id="rfc.xref.RFC2965.1"><cite title="HTTP State Management Mechanism">[RFC2965]</cite></a> does not share this problem. 
    11731173         </p>  
  • draft-ietf-httpbis/latest/p1-messaging.xml

    r754 r756  
    11681168<x:note> 
    11691169  <t> 
    1170    <x:h>Note:</x:h> the "Set-Cookie" header as implemented in 
     1170   <x:h>Note:</x:h> The "Set-Cookie" header as implemented in 
    11711171   practice (as opposed to how it is specified in <xref target="RFC2109"/>) 
    11721172   can occur multiple times, but does not use the list syntax, and thus cannot 
  • draft-ietf-httpbis/latest/p2-semantics.html

    r754 r756  
    403403      <meta name="dct.creator" content="Reschke, J. F."> 
    404404      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest"> 
    405       <meta name="dct.issued" scheme="ISO8601" content="2010-02-01"> 
     405      <meta name="dct.issued" scheme="ISO8601" content="2010-02-02"> 
    406406      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    407407      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 2 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 2 defines the semantics of HTTP messages as expressed by request methods, request-header fields, response status codes, and response-header fields."> 
     
    434434            </tr> 
    435435            <tr> 
    436                <td class="left">Expires: August 5, 2010</td> 
     436               <td class="left">Expires: August 6, 2010</td> 
    437437               <td class="right">HP</td> 
    438438            </tr> 
     
    487487            <tr> 
    488488               <td class="left"></td> 
    489                <td class="right">February 1, 2010</td> 
     489               <td class="right">February 2, 2010</td> 
    490490            </tr> 
    491491         </tbody> 
     
    518518      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 
    519519      </p> 
    520       <p>This Internet-Draft will expire in August 5, 2010.</p> 
     520      <p>This Internet-Draft will expire in August 6, 2010.</p> 
    521521      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    522522      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    12111211      </p> 
    12121212      <div class="note" id="rfc.section.8.3.p.2">  
    1213          <p> <b>Note:</b> an earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers should be aware that there might be clients that implement such a fixed limitation. 
     1213         <p> <b>Note:</b> An earlier version of this specification recommended a maximum of five redirections (<a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-10.3">Section 10.3</a>). Content developers should be aware that there might be clients that implement such a fixed limitation. 
    12141214         </p>  
    12151215      </div> 
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r754 r756  
    12871287<x:note> 
    12881288  <t> 
    1289     <x:h>Note:</x:h> an earlier version of this specification recommended a 
     1289    <x:h>Note:</x:h> An earlier version of this specification recommended a 
    12901290    maximum of five redirections (<xref target="RFC2068" x:fmt="," x:sec="10.3"/>). 
    12911291    Content developers should be aware that there might be clients that 
  • draft-ietf-httpbis/latest/p3-payload.html

    r754 r756  
    401401      <meta name="dct.creator" content="Reschke, J. F."> 
    402402      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p3-payload-latest"> 
    403       <meta name="dct.issued" scheme="ISO8601" content="2010-02-01"> 
     403      <meta name="dct.issued" scheme="ISO8601" content="2010-02-02"> 
    404404      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    405405      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 3 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 3 defines HTTP message content, metadata, and content negotiation."> 
     
    427427            </tr> 
    428428            <tr> 
    429                <td class="left">Expires: August 5, 2010</td> 
     429               <td class="left">Expires: August 6, 2010</td> 
    430430               <td class="right">J. Mogul</td> 
    431431            </tr> 
     
    484484            <tr> 
    485485               <td class="left"></td> 
    486                <td class="right">February 1, 2010</td> 
     486               <td class="right">February 2, 2010</td> 
    487487            </tr> 
    488488         </tbody> 
     
    514514      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 
    515515      </p> 
    516       <p>This Internet-Draft will expire in August 5, 2010.</p> 
     516      <p>This Internet-Draft will expire in August 6, 2010.</p> 
    517517      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    518518      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    11941194      </p> 
    11951195      <div class="note" id="rfc.section.5.4.p.7">  
    1196          <p> <b>Note:</b> the "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined in <a href="http://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. 
     1196         <p> <b>Note:</b> The "Basic Filtering" scheme (<a href="#RFC4647" id="rfc.xref.RFC4647.4"><cite title="Matching of Language Tags">[RFC4647]</cite></a>, <a href="http://tools.ietf.org/html/rfc4647#section-3.3.1">Section 3.3.1</a>) is identical to the matching scheme that was previously defined in <a href="http://tools.ietf.org/html/rfc2616#section-14.4">Section 14.4</a> of <a href="#RFC2616" id="rfc.xref.RFC2616.2"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2616]</cite></a>. 
    11971197         </p>  
    11981198      </div> 
     
    13121312      </p> 
    13131313      <div class="note" id="rfc.section.5.8.p.9">  
    1314          <p> <b>Note:</b> while the definition of Content-MD5 is exactly the same for HTTP as in RFC 1864 for MIME entity-bodies, there are several 
     1314         <p> <b>Note:</b> While the definition of Content-MD5 is exactly the same for HTTP as in RFC 1864 for MIME entity-bodies, there are several 
    13151315            ways in which the application of Content-MD5 to HTTP entity-bodies differs from its application to MIME entity-bodies. One 
    13161316            is that HTTP, unlike MIME, does not use Content-Transfer-Encoding, and does use Transfer-Encoding and Content-Encoding. Another 
  • draft-ietf-httpbis/latest/p3-payload.xml

    r754 r756  
    12701270<x:note> 
    12711271  <t> 
    1272     <x:h>Note:</x:h> the "Basic Filtering" scheme (<xref target="RFC4647" 
     1272    <x:h>Note:</x:h> The "Basic Filtering" scheme (<xref target="RFC4647" 
    12731273    x:fmt="," x:sec="3.3.1"/>) is identical to the matching scheme that was 
    12741274    previously defined in <xref target="RFC2616" x:fmt="of" x:sec="14.4"/>. 
     
    15171517<x:note> 
    15181518  <t> 
    1519     <x:h>Note:</x:h> while the definition of Content-MD5 is exactly the same for 
     1519    <x:h>Note:</x:h> While the definition of Content-MD5 is exactly the same for 
    15201520    HTTP as in RFC 1864 for MIME entity-bodies, there are several ways 
    15211521    in which the application of Content-MD5 to HTTP entity-bodies 
  • draft-ietf-httpbis/latest/p4-conditional.html

    r755 r756  
    400400      <meta name="dct.creator" content="Reschke, J. F."> 
    401401      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest"> 
    402       <meta name="dct.issued" scheme="ISO8601" content="2010-02-01"> 
     402      <meta name="dct.issued" scheme="ISO8601" content="2010-02-02"> 
    403403      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    404404      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 4 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 4 defines request header fields for indicating conditional requests and the rules for constructing responses to those requests."> 
     
    426426            </tr> 
    427427            <tr> 
    428                <td class="left">Expires: August 5, 2010</td> 
     428               <td class="left">Expires: August 6, 2010</td> 
    429429               <td class="right">J. Mogul</td> 
    430430            </tr> 
     
    483483            <tr> 
    484484               <td class="left"></td> 
    485                <td class="right">February 1, 2010</td> 
     485               <td class="right">February 2, 2010</td> 
    486486            </tr> 
    487487         </tbody> 
     
    513513      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 
    514514      </p> 
    515       <p>This Internet-Draft will expire in August 5, 2010.</p> 
     515      <p>This Internet-Draft will expire in August 6, 2010.</p> 
    516516      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    517517      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    819819      </p> 
    820820      <div class="note" id="rfc.section.5.p.5">  
    821          <p> <b>Note:</b> in order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity tag value 
     821         <p> <b>Note:</b> In order to provide semantically transparent caching, an origin server must avoid reusing a specific strong entity tag value 
    822822            for two different entities, or reusing a specific weak entity tag value for two semantically different entities. Cache entries 
    823823            might persist for arbitrarily long periods, regardless of expiration times, so it might be inappropriate to expect that a 
  • draft-ietf-httpbis/latest/p4-conditional.xml

    r755 r756  
    607607<x:note> 
    608608  <t> 
    609     <x:h>Note:</x:h> in order to provide semantically transparent caching, an 
     609    <x:h>Note:</x:h> In order to provide semantically transparent caching, an 
    610610    origin server must avoid reusing a specific strong entity tag 
    611611    value for two different entities, or reusing a specific weak 
  • draft-ietf-httpbis/latest/p5-range.html

    r754 r756  
    400400      <meta name="dct.creator" content="Reschke, J. F."> 
    401401      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p5-range-latest"> 
    402       <meta name="dct.issued" scheme="ISO8601" content="2010-02-01"> 
     402      <meta name="dct.issued" scheme="ISO8601" content="2010-02-02"> 
    403403      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    404404      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. HTTP has been in use by the World Wide Web global information initiative since 1990. This document is Part 5 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 5 defines range-specific requests and the rules for constructing and combining responses to those requests."> 
     
    426426            </tr> 
    427427            <tr> 
    428                <td class="left">Expires: August 5, 2010</td> 
     428               <td class="left">Expires: August 6, 2010</td> 
    429429               <td class="right">J. Mogul</td> 
    430430            </tr> 
     
    483483            <tr> 
    484484               <td class="left"></td> 
    485                <td class="right">February 1, 2010</td> 
     485               <td class="right">February 2, 2010</td> 
    486486            </tr> 
    487487         </tbody> 
     
    513513      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 
    514514      </p> 
    515       <p>This Internet-Draft will expire in August 5, 2010.</p> 
     515      <p>This Internet-Draft will expire in August 6, 2010.</p> 
    516516      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    517517      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    788788      </p> 
    789789      <div class="note" id="rfc.section.5.2.p.15">  
    790          <p> <b>Note:</b> clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for 
     790         <p> <b>Note:</b> Clients cannot depend on servers to send a 416 (Requested range not satisfiable) response instead of a 200 (OK) response for 
    791791            an unsatisfiable Range request-header, since not all servers implement this request-header. 
    792792         </p>  
  • draft-ietf-httpbis/latest/p5-range.xml

    r754 r756  
    632632<x:note> 
    633633  <t> 
    634     <x:h>Note:</x:h> clients cannot depend on servers to send a 416 (Requested 
     634    <x:h>Note:</x:h> Clients cannot depend on servers to send a 416 (Requested 
    635635    range not satisfiable) response instead of a 200 (OK) response for 
    636636    an unsatisfiable Range request-header, since not all servers 
  • draft-ietf-httpbis/latest/p6-cache.html

    r754 r756  
    402402      <meta name="dct.creator" content="Reschke, J. F."> 
    403403      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest"> 
    404       <meta name="dct.issued" scheme="ISO8601" content="2010-02-01"> 
     404      <meta name="dct.issued" scheme="ISO8601" content="2010-02-02"> 
    405405      <meta name="dct.replaces" content="urn:ietf:rfc:2616"> 
    406406      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems. This document is Part 6 of the seven-part specification that defines the protocol referred to as &#34;HTTP/1.1&#34; and, taken together, obsoletes RFC 2616. Part 6 defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages."> 
     
    428428            </tr> 
    429429            <tr> 
    430                <td class="left">Expires: August 5, 2010</td> 
     430               <td class="left">Expires: August 6, 2010</td> 
    431431               <td class="right">J. Mogul</td> 
    432432            </tr> 
     
    489489            <tr> 
    490490               <td class="left"></td> 
    491                <td class="right">February 1, 2010</td> 
     491               <td class="right">February 2, 2010</td> 
    492492            </tr> 
    493493         </tbody> 
     
    519519      <p>The list of Internet-Draft Shadow Directories can be accessed at <a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>. 
    520520      </p> 
    521       <p>This Internet-Draft will expire in August 5, 2010.</p> 
     521      <p>This Internet-Draft will expire in August 6, 2010.</p> 
    522522      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1> 
    523523      <p>Copyright © 2010 IETF Trust and the persons identified as the document authors. All rights reserved.</p> 
     
    12301230      <p>For example</p>  <pre class="text">  Expires: Thu, 01 Dec 1994 16:00:00 GMT 
    12311231</pre><div class="note" id="rfc.section.3.3.p.6">  
    1232          <p> <b>Note:</b> if a response includes a Cache-Control field with the max-age directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), that directive overrides the Expires field. Likewise, the s-maxage directive overrides Expires in shared caches. 
     1232         <p> <b>Note:</b> If a response includes a Cache-Control field with the max-age directive (see <a href="#cache-response-directive" title="Response Cache-Control Directives">Section&nbsp;3.2.2</a>), that directive overrides the Expires field. Likewise, the s-maxage directive overrides Expires in shared caches. 
    12331233         </p>  
    12341234      </div> 
     
    12521252      </p> 
    12531253      <div class="note" id="rfc.section.3.4.p.4">  
    1254          <p> <b>Note:</b> because the meaning of "Pragma: no-cache" as a response-header field is not actually specified, it does not provide a reliable 
     1254         <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" as a response-header field is not actually specified, it does not provide a reliable 
    12551255            replacement for "Cache-Control: no-cache" in a response. 
    12561256         </p>  
     
    13851385      <p id="rfc.section.4.p.4">This is not to be construed to prohibit the history mechanism from telling the user that a view might be stale.</p> 
    13861386      <div class="note" id="rfc.section.4.p.5">  
    1387          <p> <b>Note:</b> if history list mechanisms unnecessarily prevent users from viewing stale resources, this will tend to force service authors 
     1387         <p> <b>Note:</b> If history list mechanisms unnecessarily prevent users from viewing stale resources, this will tend to force service authors 
    13881388            to avoid using HTTP expiration controls and cache controls when they would otherwise like to. Service authors may consider 
    13891389            it important that users not be presented with error messages or warning messages when they use navigation controls (such as 
  • draft-ietf-httpbis/latest/p6-cache.xml

    r754 r756  
    12951295<x:note> 
    12961296  <t> 
    1297     <x:h>Note:</x:h> if a response includes a Cache-Control field with the max-age 
     1297    <x:h>Note:</x:h> If a response includes a Cache-Control field with the max-age 
    12981298    directive (see <xref target="cache-response-directive" />), that directive overrides 
    12991299    the Expires field. Likewise, the s-maxage directive overrides Expires in shared caches. 
     
    13391339<x:note> 
    13401340  <t> 
    1341     <x:h>Note:</x:h> because the meaning of "Pragma: no-cache" as a response-header field 
     1341    <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" as a response-header field 
    13421342    is not actually specified, it does not provide a reliable replacement for 
    13431343    "Cache-Control: no-cache" in a response. 
     
    15611561<x:note> 
    15621562  <t> 
    1563     <x:h>Note:</x:h> if history list mechanisms unnecessarily prevent users from viewing 
     1563    <x:h>Note:</x:h> If history list mechanisms unnecessarily prevent users from viewing 
    15641564    stale resources, this will tend to force service authors to avoid using HTTP expiration 
    15651565    controls and cache controls when they would otherwise like to. Service authors may 
Note: See TracChangeset for help on using the changeset viewer.