Changeset 2577


Ignore:
Timestamp:
24/01/14 09:14:55 (6 years ago)
Author:
fielding@…
Message:

(editorial) clarify a run-on sentence; see #520

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

Legend:

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

    r2569 r2577  
    448448  }
    449449  @bottom-center {
    450        content: "Expires July 27, 2014";
     450       content: "Expires July 28, 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="2014-01-23">
     495      <meta name="dct.issued" scheme="ISO8601" content="2014-01-24">
    496496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    497497      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless 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">January 23, 2014</td>
     523               <td class="right">January 24, 2014</td>
    524524            </tr>
    525525            <tr>
    526                <td class="left">Expires: July 27, 2014</td>
     526               <td class="left">Expires: July 28, 2014</td>
    527527               <td class="right"></td>
    528528            </tr>
     
    553553            in progress”.
    554554         </p>
    555          <p>This Internet-Draft will expire on July 27, 2014.</p>
     555         <p>This Internet-Draft will expire on July 28, 2014.</p>
    556556      </div>
    557557      <div id="rfc.copyrightnotice">
     
    12781278                  the user agent's preferences is better than sending a <a href="#status.406" class="smpl">406 (Not Acceptable)</a> response.
    12791279               </p>
    1280                <p id="rfc.section.3.4.1.p.5">An origin server <em class="bcp14">MAY</em> generate a <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;7.1.4</a>) in responses that are subject to proactive negotiation to indicate what parameters of request information might be used
    1281                   in its selection algorithm, thereby providing a means for recipients to determine the reusability of that same response for
    1282                   user agents with differing request information.
     1280               <p id="rfc.section.3.4.1.p.5">An origin server <em class="bcp14">MAY</em> generate a <a href="#header.vary" class="smpl">Vary</a> header field (<a href="#header.vary" id="rfc.xref.header.vary.1" title="Vary">Section&nbsp;7.1.4</a>) in a response if it wishes to indicate what fields of request information were used in its selection algorithm. This informs
     1281                  recipients that sending more information might be useful in future requests. It also warns caches not to reuse that response,
     1282                  until reconfirmed by the origin server, for a request that contains different information in those fields.
    12831283               </p>
    12841284            </div>
     
    21612161                     <tr>
    21622162                        <td class="left">Authorization</td>
    2163                         <td class="left"><a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     2163                        <td class="left"><a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.3"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
    21642164                     </tr>
    21652165                     <tr>
    21662166                        <td class="left">Proxy-Authorization</td>
    2167                         <td class="left"><a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.3</a> of <a href="#Part7" id="rfc.xref.Part7.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     2167                        <td class="left"><a href="p7-auth.html#header.proxy-authorization" title="Proxy-Authorization">Section 4.4</a> of <a href="#Part7" id="rfc.xref.Part7.4"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
    21682168                     </tr>
    21692169                  </tbody>
     
    33133313                  other than the method and request target, unless the variance cannot be crossed or the origin server has been deliberately
    33143314                  configured to prevent cache transparency. For example, there is no need to send the Authorization field name in Vary because
    3315                   reuse across users is constrained by the field definition (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>). Likewise, an origin server might use Cache-Control directives (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#Part6" id="rfc.xref.Part6.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to supplant Vary if it considers the variance less significant than the performance cost of Vary's impact on caching.
     3315                  reuse across users is constrained by the field definition (<a href="p7-auth.html#header.authorization" title="Authorization">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.8"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a>). Likewise, an origin server might use Cache-Control directives (<a href="p6-cache.html#header.cache-control" title="Cache-Control">Section 5.2</a> of <a href="#Part6" id="rfc.xref.Part6.27"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Caching">[Part6]</cite></a>) to supplant Vary if it considers the variance less significant than the performance cost of Vary's impact on caching.
    33163316               </p>
    33173317            </div>
     
    33663366                     <tr>
    33673367                        <td class="left">WWW-Authenticate</td>
    3368                         <td class="left"><a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.4</a> of <a href="#Part7" id="rfc.xref.Part7.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     3368                        <td class="left"><a href="p7-auth.html#header.www-authenticate" title="WWW-Authenticate">Section 4.1</a> of <a href="#Part7" id="rfc.xref.Part7.9"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
    33693369                     </tr>
    33703370                     <tr>
    33713371                        <td class="left">Proxy-Authenticate</td>
    3372                         <td class="left"><a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.2</a> of <a href="#Part7" id="rfc.xref.Part7.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
     3372                        <td class="left"><a href="p7-auth.html#header.proxy-authenticate" title="Proxy-Authenticate">Section 4.3</a> of <a href="#Part7" id="rfc.xref.Part7.10"><cite title="Hypertext Transfer Protocol (HTTP/1.1): Authentication">[Part7]</cite></a></td>
    33733373                     </tr>
    33743374                  </tbody>
     
    50655065                        <li><em>Section 3.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.6">6.1</a></li>
    50665066                        <li><em>Section 3.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.7">6.1</a></li>
    5067                         <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.3">5.4</a>, <a href="#rfc.xref.Part7.8">7.1.4</a></li>
    5068                         <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.10">7.3</a></li>
    5069                         <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.4">5.4</a></li>
    5070                         <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.9">7.3</a></li>
     5067                        <li><em>Section 4.1</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.9">7.3</a></li>
     5068                        <li><em>Section 4.2</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.3">5.4</a>, <a href="#rfc.xref.Part7.8">7.1.4</a></li>
     5069                        <li><em>Section 4.3</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.10">7.3</a></li>
     5070                        <li><em>Section 4.4</em>&nbsp;&nbsp;<a href="#rfc.xref.Part7.4">5.4</a></li>
    50715071                     </ul>
    50725072                  </li>
  • draft-ietf-httpbis/latest/p2-semantics.xml

    r2569 r2577  
    10201020<t>
    10211021   An origin server &MAY; generate a <x:ref>Vary</x:ref> header field
    1022    (<xref target="header.vary"/>) in responses that are subject to proactive
    1023    negotiation to indicate what parameters of request information might
    1024    be used in its selection algorithm, thereby providing a means for
    1025    recipients to determine the reusability of that same response for
    1026    user agents with differing request information.
     1022   (<xref target="header.vary"/>) in a response if it wishes to indicate what
     1023   fields of request information were used in its selection algorithm. This
     1024   informs recipients that sending more information might be useful in future
     1025   requests. It also warns caches not to reuse that response, until
     1026   reconfirmed by the origin server, for a request that contains different
     1027   information in those fields.
    10271028</t>
    10281029</section>
  • draft-ietf-httpbis/latest/p7-auth.html

    r2576 r2577  
    448448  }
    449449  @bottom-center {
    450        content: "Expires July 27, 2014";
     450       content: "Expires July 28, 2014";
    451451  }
    452452  @bottom-right {
     
    488488      <meta name="dct.creator" content="Reschke, J. F.">
    489489      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p7-auth-latest">
    490       <meta name="dct.issued" scheme="ISO8601" content="2014-01-23">
     490      <meta name="dct.issued" scheme="ISO8601" content="2014-01-24">
    491491      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    492492      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is a stateless application-level protocol for distributed, collaborative, hypermedia information systems. This document defines the HTTP Authentication framework.">
     
    516516            <tr>
    517517               <td class="left">Intended status: Standards Track</td>
    518                <td class="right">January 23, 2014</td>
     518               <td class="right">January 24, 2014</td>
    519519            </tr>
    520520            <tr>
    521                <td class="left">Expires: July 27, 2014</td>
     521               <td class="left">Expires: July 28, 2014</td>
    522522               <td class="right"></td>
    523523            </tr>
     
    546546            in progress”.
    547547         </p>
    548          <p>This Internet-Draft will expire on July 27, 2014.</p>
     548         <p>This Internet-Draft will expire on July 28, 2014.</p>
    549549      </div>
    550550      <div id="rfc.copyrightnotice">
Note: See TracChangeset for help on using the changeset viewer.