Ignore:
Timestamp:
May 20, 2011, 12:06:38 AM (9 years ago)
Author:
julian.reschke@…
Message:

editorial: remove tabs, tune markup, regen HTML

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

Legend:

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

    r1283 r1287  
    359359  }
    360360  @bottom-center {
    361        content: "Expires November 20, 2011";
     361       content: "Expires November 21, 2011";
    362362  }
    363363  @bottom-right {
     
    409409      <meta name="dct.creator" content="Reschke, J. F.">
    410410      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p2-semantics-latest">
    411       <meta name="dct.issued" scheme="ISO8601" content="2011-05-19">
     411      <meta name="dct.issued" scheme="ISO8601" content="2011-05-20">
    412412      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    413413      <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.">
     
    440440            </tr>
    441441            <tr>
    442                <td class="left">Expires: November 20, 2011</td>
     442               <td class="left">Expires: November 21, 2011</td>
    443443               <td class="right">HP</td>
    444444            </tr>
     
    493493            <tr>
    494494               <td class="left"></td>
    495                <td class="right">May 19, 2011</td>
     495               <td class="right">May 20, 2011</td>
    496496            </tr>
    497497         </tbody>
     
    522522         in progress”.
    523523      </p>
    524       <p>This Internet-Draft will expire on November 20, 2011.</p>
     524      <p>This Internet-Draft will expire on November 21, 2011.</p>
    525525      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    526526      <p>Copyright © 2011 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
  • draft-ietf-httpbis/latest/p6-cache.html

    r1284 r1287  
    837837         with the effect of either increasing or loosening constraints on freshness. See <a href="#cache-request-directive" title="Request Cache-Control Directives">Section&nbsp;3.2.1</a>.
    838838      </p>
    839       <p id="rfc.section.2.3.p.8"> <span class="comment" id="ISSUE-no-req-for-directives">[<a href="#ISSUE-no-req-for-directives" class="smpl">ISSUE-no-req-for-directives</a>: there are not requirements directly applying to cache-request-directives and freshness.]</span>
    840       </p>
    841       <p id="rfc.section.2.3.p.9">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
     839      <p id="rfc.section.2.3.p.8">Note that freshness applies only to cache operation; it cannot be used to force a user agent to refresh its display or reload
    842840         a resource. See <a href="#history.lists" title="History Lists">Section&nbsp;4</a> for an explanation of the difference between caches and history mechanisms.
    843841      </p>
     
    12661264         it will also see and understand the private directive and thus default to the safe behavior.
    12671265      </p>
    1268       <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> be ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
     1266      <p id="rfc.section.3.2.3.p.6">A cache <em class="bcp14">MUST</em> ignore unrecognized cache directives; it is assumed that any cache directive likely to be unrecognized by an HTTP/1.1 cache
    12691267         will be combined with standard directives (or the response's default cacheability) such that the cache behavior will remain
    12701268         minimally correct even if the cache does not understand the extension(s).
     
    13241322Cache-Control: max-age=30
    13251323Pragma: no-cache
     1324
    13261325</pre> <p id="rfc.section.3.4.p.7">will constrain HTTP/1.1 caches to serve a response no older than 30 seconds, while precluding implementations that do not
    13271326         understand Cache-Control from serving a cached response.
    13281327      </p>
    13291328      <div class="note" id="rfc.section.3.4.p.8">
    1330          <p>Note: Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement
    1331             for "Cache-Control: no-cache" in them.
     1329         <p> <b>Note:</b> Because the meaning of "Pragma: no-cache" in responses is not specified, it does not provide a reliable replacement for "Cache-Control:
     1330            no-cache" in them.
    13321331         </p>
    13331332      </div>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r1286 r1287  
    14981498   <x:anchor-alias value="pragma-directive"/>
    14991499<t>
    1500         The "Pragma" header field allows backwards compatibility with HTTP/1.0
     1500  The "Pragma" header field allows backwards compatibility with HTTP/1.0
    15011501   caches, so that clients can specify a "no-cache" request that they will
    15021502   understand (as Cache-Control was not defined until HTTP/1.1). When the
     
    15051505</t>
    15061506<t>
    1507         In HTTP/1.0, Pragma was defined as an extensible field for
     1507  In HTTP/1.0, Pragma was defined as an extensible field for
    15081508   implementation-specified directives for recipients. This specification
    15091509   deprecates such extensions to improve interoperability.
     
    15151515</artwork></figure>
    15161516<t>
    1517         When the Cache-Control header is not present in a request, the no-cache
     1517  When the Cache-Control header is not present in a request, the no-cache
    15181518   request pragma-directive &MUST; have the same effect on caches as if
    15191519   "Cache-Control: no-cache" were present (see <xref
     
    15271527</t>
    15281528<figure>
    1529 <artwork type="code">
     1529<artwork type="message/http; msgtype=&#34;response&#34;" x:indent-with="  ">
    15301530GET / HTTP/1.1
    15311531Host: www.example.com
    15321532Cache-Control: max-age=30
    15331533Pragma: no-cache
     1534
    15341535</artwork>
    15351536</figure>
     
    15411542<x:note>
    15421543   <t>
    1543       Note: Because the meaning of "Pragma: no-cache" in responses is not
     1544      <x:h>Note:</x:h> Because the meaning of "Pragma: no-cache" in responses is not
    15441545      specified, it does not provide a reliable replacement for
    15451546      "Cache-Control: no-cache" in them.
    1546         </t>
     1547  </t>
    15471548</x:note>
    15481549</section>
     
    26012602      "Clarify differences between / requirements for request and response CC directives"
    26022603    </t>
    2603         <t>
    2604                 <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/174" />:
    2605                 "Caching authenticated responses"
    2606         </t>
     2604    <t>
     2605      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/174" />:
     2606      "Caching authenticated responses"
     2607    </t>
    26072608    <t>
    26082609      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/208" />:
     
    26962697<t>
    26972698  Closed issues:
    2698         <list style="symbols">
    2699                 <t>
    2700                         <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/292"/>:
    2701                         "Pragma"
    2702                 </t>
    2703         </list>
     2699  <list style="symbols">
     2700    <t>
     2701      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/292"/>:
     2702      "Pragma"
     2703    </t>
     2704  </list>
    27042705</t>
    27052706</section>
Note: See TracChangeset for help on using the changeset viewer.