Ignore:
Timestamp:
Dec 1, 2009, 12:11:18 AM (10 years ago)
Author:
julian.reschke@…
Message:

Bump up document dates, update to latest versions of rfc2629.xslt

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p6-cache.html

    r728 r729  
    4040}
    4141
    42 dl.empty dd {
     42ul.empty {
     43  list-style-type: none;
     44}
     45ul.empty li {
    4346  margin-top: .5em;
    4447}
     
    170173
    171174table.header {
     175  border-spacing: 1px;
    172176  width: 95%;
    173177  font-size: 10pt;
     
    181185  white-space: nowrap;
    182186}
    183 td.header {
     187table.header td {
    184188  background-color: gray;
    185189  width: 50%;
    186190}
    187 td.header a {
     191table.header a {
    188192  color: white;
    189193}
     
    343347  }
    344348  @top-right {
    345        content: "November 2009";
     349       content: "December 2009";
    346350  }
    347351  @top-center {
     
    385389      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    386390      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    387       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.478, 2009-10-16 14:30:15, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     391      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.485, 2009-11-28 15:36:33, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    388392      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    389393      <meta name="DC.Creator" content="Fielding, R.">
     
    398402      <meta name="DC.Creator" content="Reschke, J. F.">
    399403      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    400       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-11-27">
     404      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-12-01">
    401405      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    402406      <meta name="DC.Description.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.">
     
    404408   </head>
    405409   <body>
    406       <table class="header" border="0" cellpadding="1" cellspacing="1">
    407          <tr>
    408             <td class="header left">HTTPbis Working Group</td>
    409             <td class="header right">R. Fielding, Editor</td>
    410          </tr>
    411          <tr>
    412             <td class="header left">Internet Draft</td>
    413             <td class="header right">Day Software</td>
    414          </tr>
    415          <tr>
    416             <td class="header left">
    417                &lt;draft-ietf-httpbis-p6-cache-latest&gt;
    418                
    419             </td>
    420             <td class="header right">J. Gettys</td>
    421          </tr>
    422          <tr>
    423             <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    424             </td>
    425             <td class="header right">One Laptop per Child</td>
    426          </tr>
    427          <tr>
    428             <td class="header left">Intended status: Standards Track</td>
    429             <td class="header right">J. Mogul</td>
    430          </tr>
    431          <tr>
    432             <td class="header left">Expires: May 31, 2010</td>
    433             <td class="header right">HP</td>
    434          </tr>
    435          <tr>
    436             <td class="header left"></td>
    437             <td class="header right">H. Frystyk</td>
    438          </tr>
    439          <tr>
    440             <td class="header left"></td>
    441             <td class="header right">Microsoft</td>
    442          </tr>
    443          <tr>
    444             <td class="header left"></td>
    445             <td class="header right">L. Masinter</td>
    446          </tr>
    447          <tr>
    448             <td class="header left"></td>
    449             <td class="header right">Adobe Systems</td>
    450          </tr>
    451          <tr>
    452             <td class="header left"></td>
    453             <td class="header right">P. Leach</td>
    454          </tr>
    455          <tr>
    456             <td class="header left"></td>
    457             <td class="header right">Microsoft</td>
    458          </tr>
    459          <tr>
    460             <td class="header left"></td>
    461             <td class="header right">T. Berners-Lee</td>
    462          </tr>
    463          <tr>
    464             <td class="header left"></td>
    465             <td class="header right">W3C/MIT</td>
    466          </tr>
    467          <tr>
    468             <td class="header left"></td>
    469             <td class="header right">Y. Lafon, Editor</td>
    470          </tr>
    471          <tr>
    472             <td class="header left"></td>
    473             <td class="header right">W3C</td>
    474          </tr>
    475          <tr>
    476             <td class="header left"></td>
    477             <td class="header right">M. Nottingham, Editor</td>
    478          </tr>
    479          <tr>
    480             <td class="header left"></td>
    481             <td class="header right">J. F. Reschke, Editor</td>
    482          </tr>
    483          <tr>
    484             <td class="header left"></td>
    485             <td class="header right">greenbytes</td>
    486          </tr>
    487          <tr>
    488             <td class="header left"></td>
    489             <td class="header right">November 27, 2009</td>
    490          </tr>
     410      <table class="header">
     411         <tbody>
     412            <tr>
     413               <td class="left">HTTPbis Working Group</td>
     414               <td class="right">R. Fielding, Editor</td>
     415            </tr>
     416            <tr>
     417               <td class="left">Internet Draft</td>
     418               <td class="right">Day Software</td>
     419            </tr>
     420            <tr>
     421               <td class="left">
     422                  &lt;draft-ietf-httpbis-p6-cache-latest&gt;
     423                 
     424               </td>
     425               <td class="right">J. Gettys</td>
     426            </tr>
     427            <tr>
     428               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     429               </td>
     430               <td class="right">One Laptop per Child</td>
     431            </tr>
     432            <tr>
     433               <td class="left">Intended status: Standards Track</td>
     434               <td class="right">J. Mogul</td>
     435            </tr>
     436            <tr>
     437               <td class="left">Expires: June 4, 2010</td>
     438               <td class="right">HP</td>
     439            </tr>
     440            <tr>
     441               <td class="left"></td>
     442               <td class="right">H. Frystyk</td>
     443            </tr>
     444            <tr>
     445               <td class="left"></td>
     446               <td class="right">Microsoft</td>
     447            </tr>
     448            <tr>
     449               <td class="left"></td>
     450               <td class="right">L. Masinter</td>
     451            </tr>
     452            <tr>
     453               <td class="left"></td>
     454               <td class="right">Adobe Systems</td>
     455            </tr>
     456            <tr>
     457               <td class="left"></td>
     458               <td class="right">P. Leach</td>
     459            </tr>
     460            <tr>
     461               <td class="left"></td>
     462               <td class="right">Microsoft</td>
     463            </tr>
     464            <tr>
     465               <td class="left"></td>
     466               <td class="right">T. Berners-Lee</td>
     467            </tr>
     468            <tr>
     469               <td class="left"></td>
     470               <td class="right">W3C/MIT</td>
     471            </tr>
     472            <tr>
     473               <td class="left"></td>
     474               <td class="right">Y. Lafon, Editor</td>
     475            </tr>
     476            <tr>
     477               <td class="left"></td>
     478               <td class="right">W3C</td>
     479            </tr>
     480            <tr>
     481               <td class="left"></td>
     482               <td class="right">M. Nottingham, Editor</td>
     483            </tr>
     484            <tr>
     485               <td class="left"></td>
     486               <td class="right">J. F. Reschke, Editor</td>
     487            </tr>
     488            <tr>
     489               <td class="left"></td>
     490               <td class="right">greenbytes</td>
     491            </tr>
     492            <tr>
     493               <td class="left"></td>
     494               <td class="right">December 1, 2009</td>
     495            </tr>
     496         </tbody>
    491497      </table>
    492498      <p class="title">HTTP/1.1, part 6: Caching<br><span class="filename">draft-ietf-httpbis-p6-cache-latest</span></p>
     
    516522      <p>The list of Internet-Draft Shadow Directories can be accessed at &lt;<a href="http://www.ietf.org/shadow.html">http://www.ietf.org/shadow.html</a>&gt;.
    517523      </p>
    518       <p>This Internet-Draft will expire in May 31, 2010.</p>
     524      <p>This Internet-Draft will expire in June 4, 2010.</p>
    519525      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    520526      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    632638      <p id="rfc.section.1.2.p.2"> <span id="rfc.iref.c.2"></span>  <dfn>cacheable</dfn> 
    633639      </p>
    634       <dl class="empty">
    635          <dd>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
     640      <ul class="empty">
     641         <li>A response is cacheable if a cache is allowed to store a copy of the response message for use in answering subsequent requests.
    636642            Even when a response is cacheable, there may be additional constraints on whether a cache can use the cached copy to satisfy
    637643            a particular request.
    638          </dd>
    639       </dl>
     644         </li>
     645      </ul>
    640646      <p id="rfc.section.1.2.p.3"> <span id="rfc.iref.e.1"></span>  <dfn>explicit expiration time</dfn> 
    641647      </p>
    642       <dl class="empty">
    643          <dd>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</dd>
    644       </dl>
     648      <ul class="empty">
     649         <li>The time at which the origin server intends that an entity should no longer be returned by a cache without further validation.</li>
     650      </ul>
    645651      <p id="rfc.section.1.2.p.4"> <span id="rfc.iref.h.1"></span>  <dfn>heuristic expiration time</dfn> 
    646652      </p>
    647       <dl class="empty">
    648          <dd>An expiration time assigned by a cache when no explicit expiration time is available.</dd>
    649       </dl>
     653      <ul class="empty">
     654         <li>An expiration time assigned by a cache when no explicit expiration time is available.</li>
     655      </ul>
    650656      <p id="rfc.section.1.2.p.5"> <span id="rfc.iref.a.1"></span>  <dfn>age</dfn> 
    651657      </p>
    652       <dl class="empty">
    653          <dd>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</dd>
    654       </dl>
     658      <ul class="empty">
     659         <li>The age of a response is the time since it was sent by, or successfully validated with, the origin server.</li>
     660      </ul>
    655661      <p id="rfc.section.1.2.p.6"> <span id="rfc.iref.f.1"></span>  <dfn>first-hand</dfn> 
    656662      </p>
    657       <dl class="empty">
    658          <dd>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</dd>
    659       </dl>
     663      <ul class="empty">
     664         <li>A response is first-hand if the freshness model is not in use; i.e., its age is 0.</li>
     665      </ul>
    660666      <p id="rfc.section.1.2.p.7"> <span id="rfc.iref.f.2"></span>  <dfn>freshness lifetime</dfn> 
    661667      </p>
    662       <dl class="empty">
    663          <dd>The length of time between the generation of a response and its expiration time.</dd>
    664       </dl>
     668      <ul class="empty">
     669         <li>The length of time between the generation of a response and its expiration time.</li>
     670      </ul>
    665671      <p id="rfc.section.1.2.p.8"> <span id="rfc.iref.f.3"></span>  <dfn>fresh</dfn> 
    666672      </p>
    667       <dl class="empty">
    668          <dd>A response is fresh if its age has not yet exceeded its freshness lifetime.</dd>
    669       </dl>
     673      <ul class="empty">
     674         <li>A response is fresh if its age has not yet exceeded its freshness lifetime.</li>
     675      </ul>
    670676      <p id="rfc.section.1.2.p.9"> <span id="rfc.iref.s.1"></span>  <dfn>stale</dfn> 
    671677      </p>
    672       <dl class="empty">
    673          <dd>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</dd>
    674       </dl>
     678      <ul class="empty">
     679         <li>A response is stale if its age has passed its freshness lifetime (either explicit or heuristic).</li>
     680      </ul>
    675681      <p id="rfc.section.1.2.p.10"> <span id="rfc.iref.v.1"></span>  <dfn>validator</dfn> 
    676682      </p>
    677       <dl class="empty">
    678          <dd>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a stored response is an
     683      <ul class="empty">
     684         <li>A protocol element (e.g., an entity tag or a Last-Modified time) that is used to find out whether a stored response is an
    679685            equivalent copy of an entity.
    680          </dd>
    681       </dl>
     686         </li>
     687      </ul>
    682688      <div id="shared.and.non-shared.caches">
    683689         <p id="rfc.section.1.2.p.11"> <span id="rfc.iref.v.2"></span>  <dfn>shared cache</dfn> 
    684690         </p>
    685          <dl class="empty">
    686             <dd>A cache that is accessible to more than one user. A non-shared cache is dedicated to a single user.</dd>
    687          </dl>
     691         <ul class="empty">
     692            <li>A cache that is accessible to more than one user. A non-shared cache is dedicated to a single user.</li>
     693         </ul>
    688694      </div>
    689695      <h2 id="rfc.section.1.3"><a href="#rfc.section.1.3">1.3</a>&nbsp;<a id="intro.requirements" href="#intro.requirements">Requirements</a></h2>
     
    10251031</pre><p id="rfc.section.3.2.1.p.2"> <span id="rfc.iref.c.4"></span>  <span id="rfc.iref.n.1"></span> no-cache
    10261032      </p>
    1027       <dl class="empty">
    1028          <dd>The no-cache request directive indicates that a stored response <em class="bcp14">MUST NOT</em> be used to satisfy the request without successful validation on the origin server.
    1029          </dd>
    1030       </dl>
     1033      <ul class="empty">
     1034         <li>The no-cache request directive indicates that a stored response <em class="bcp14">MUST NOT</em> be used to satisfy the request without successful validation on the origin server.
     1035         </li>
     1036      </ul>
    10311037      <p id="rfc.section.3.2.1.p.3"> <span id="rfc.iref.c.5"></span>  <span id="rfc.iref.n.2"></span> no-store
    10321038      </p>
    1033       <dl class="empty">
    1034          <dd>The no-store request directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both non-shared and shared caches.
     1039      <ul class="empty">
     1040         <li>The no-store request directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either this request or any response to it. This directive applies to both non-shared and shared caches.
    10351041            "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
    1036          </dd>
    1037          <dd>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
     1042         </li>
     1043         <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
    10381044            might not recognize or obey this directive, and communications networks may be vulnerable to eavesdropping.
    1039          </dd>
    1040       </dl>
     1045         </li>
     1046      </ul>
    10411047      <p id="rfc.section.3.2.1.p.4"> <span id="rfc.iref.c.6"></span>  <span id="rfc.iref.m.1"></span> max-age
    10421048      </p>
    1043       <dl class="empty">
    1044          <dd>The max-age request directive indicates that the client is willing to accept a response whose age is no greater than the specified
     1049      <ul class="empty">
     1050         <li>The max-age request directive indicates that the client is willing to accept a response whose age is no greater than the specified
    10451051            time in seconds. Unless max-stale directive is also included, the client is not willing to accept a stale response.
    1046          </dd>
    1047       </dl>
     1052         </li>
     1053      </ul>
    10481054      <p id="rfc.section.3.2.1.p.5"> <span id="rfc.iref.c.7"></span>  <span id="rfc.iref.m.2"></span> max-stale
    10491055      </p>
    1050       <dl class="empty">
    1051          <dd>The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration
     1056      <ul class="empty">
     1057         <li>The max-stale request directive indicates that the client is willing to accept a response that has exceeded its expiration
    10521058            time. If max-stale is assigned a value, then the client is willing to accept a response that has exceeded its expiration time
    10531059            by no more than the specified number of seconds. If no value is assigned to max-stale, then the client is willing to accept
    1054             a stale response of any age. <span class="comment" id="rfc.comment.13">[<a href="#rfc.comment.13" class="smpl">rfc.comment.13</a>: of any staleness? --mnot]</span></dd>
    1055       </dl>
     1060            a stale response of any age. <span class="comment" id="rfc.comment.13">[<a href="#rfc.comment.13" class="smpl">rfc.comment.13</a>: of any staleness? --mnot]</span></li>
     1061      </ul>
    10561062      <p id="rfc.section.3.2.1.p.6"> <span id="rfc.iref.c.8"></span>  <span id="rfc.iref.m.3"></span> min-fresh
    10571063      </p>
    1058       <dl class="empty">
    1059          <dd>The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less
     1064      <ul class="empty">
     1065         <li>The min-fresh request directive indicates that the client is willing to accept a response whose freshness lifetime is no less
    10601066            than its current age plus the specified time in seconds. That is, the client wants a response that will still be fresh for
    10611067            at least the specified number of seconds.
    1062          </dd>
    1063       </dl>
     1068         </li>
     1069      </ul>
    10641070      <p id="rfc.section.3.2.1.p.7"> <span id="rfc.iref.c.9"></span>  <span id="rfc.iref.n.3"></span> no-transform
    10651071      </p>
    1066       <dl class="empty">
    1067          <dd>The no-transform request directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type request headers, nor the request entity-body.
    1068          </dd>
    1069       </dl>
     1072      <ul class="empty">
     1073         <li>The no-transform request directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type request headers, nor the request entity-body.
     1074         </li>
     1075      </ul>
    10701076      <p id="rfc.section.3.2.1.p.8"> <span id="rfc.iref.c.10"></span>  <span id="rfc.iref.o.1"></span> only-if-cached
    10711077      </p>
    1072       <dl class="empty">
    1073          <dd>The only-if-cached request directive indicates that the client only wishes to return a stored response. If it receives this
     1078      <ul class="empty">
     1079         <li>The only-if-cached request directive indicates that the client only wishes to return a stored response. If it receives this
    10741080            directive, a cache <em class="bcp14">SHOULD</em> either respond using a stored response that is consistent with the other constraints of the request, or respond with a 504
    10751081            (Gateway Timeout) status. If a group of caches is being operated as a unified system with good internal connectivity, such
    10761082            a request <em class="bcp14">MAY</em> be forwarded within that group of caches.
    1077          </dd>
    1078       </dl>
     1083         </li>
     1084      </ul>
    10791085      <h3 id="rfc.section.3.2.2"><a href="#rfc.section.3.2.2">3.2.2</a>&nbsp;<a id="cache-response-directive" href="#cache-response-directive">Response Cache-Control Directives</a></h3>
    10801086      <div id="rfc.figure.u.11"></div><pre class="inline"><span id="rfc.iref.g.8"></span>  <a href="#header.cache-control" class="smpl">cache-response-directive</a> =
     
    10911097</pre><p id="rfc.section.3.2.2.p.2"> <span id="rfc.iref.c.11"></span>  <span id="rfc.iref.p.1"></span> public
    10921098      </p>
    1093       <dl class="empty">
    1094          <dd>The public response directive indicates that the response <em class="bcp14">MAY</em> be cached, even if it would normally be non-cacheable or cacheable only within a non-shared cache. (See also Authorization, <a href="p7-auth.html#header.authorization" title="Authorization">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, for additional details.)
    1095          </dd>
    1096       </dl>
     1099      <ul class="empty">
     1100         <li>The public response directive indicates that the response <em class="bcp14">MAY</em> be cached, even if it would normally be non-cacheable or cacheable only within a non-shared cache. (See also Authorization, <a href="p7-auth.html#header.authorization" title="Authorization">Section 3.1</a> of <a href="#Part7" id="rfc.xref.Part7.2"><cite title="HTTP/1.1, part 7: Authentication">[Part7]</cite></a>, for additional details.)
     1101         </li>
     1102      </ul>
    10971103      <p id="rfc.section.3.2.2.p.3"> <span id="rfc.iref.c.12"></span>  <span id="rfc.iref.p.2"></span> private
    10981104      </p>
    1099       <dl class="empty">
    1100          <dd>The private response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private (non-shared) cache <em class="bcp14">MAY</em> store the response.
    1101          </dd>
    1102          <dd>If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
     1105      <ul class="empty">
     1106         <li>The private response directive indicates that the response message is intended for a single user and <em class="bcp14">MUST NOT</em> be stored by a shared cache. A private (non-shared) cache <em class="bcp14">MAY</em> store the response.
     1107         </li>
     1108         <li>If the private response directive specifies one or more field-names, this requirement is limited to the field-values associated
    11031109            with the listed response headers. That is, the specified field-names(s) <em class="bcp14">MUST NOT</em> be stored by a shared cache, whereas the remainder of the response message <em class="bcp14">MAY</em> be.
    1104          </dd>
    1105          <dd> <b>Note:</b> This usage of the word private only controls where the response may be stored, and cannot ensure the privacy of the message
     1110         </li>
     1111         <li> <b>Note:</b> This usage of the word private only controls where the response may be stored, and cannot ensure the privacy of the message
    11061112            content. Also, private response directives with field-names are often handled by implementations as if an unqualified private
    11071113            directive was recieved; i.e., the special handling for the qualified form is not widely implemented.
    1108          </dd>
    1109       </dl>
     1114         </li>
     1115      </ul>
    11101116      <p id="rfc.section.3.2.2.p.4"> <span id="rfc.iref.c.13"></span>  <span id="rfc.iref.n.4"></span> no-cache
    11111117      </p>
    1112       <dl class="empty">
    1113          <dd>The no-cache response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to
     1118      <ul class="empty">
     1119         <li>The no-cache response directive indicates that the response <em class="bcp14">MUST NOT</em> be used to satisfy a subsequent request without successful validation on the origin server. This allows an origin server to
    11141120            prevent caching even by caches that have been configured to return stale responses.
    1115          </dd>
    1116          <dd>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated
     1121         </li>
     1122         <li>If the no-cache response directive specifies one or more field-names, this requirement is limited to the field-values associated
    11171123            with the listed response headers. That is, the specified field-name(s) <em class="bcp14">MUST NOT</em> be sent in the response to a subsequent request without successful validation on the origin server. This allows an origin
    11181124            server to prevent the re-use of certain header fields in a response, while still allowing caching of the rest of the response.
    1119          </dd>
    1120          <dd> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
     1125         </li>
     1126         <li> <b>Note:</b> Most HTTP/1.0 caches will not recognize or obey this directive. Also, no-cache response directives with field-names are often
    11211127            handled by implementations as if an unqualified no-cache directive was recieved; i.e., the special handling for the qualified
    11221128            form is not widely implemented.
    1123          </dd>
    1124       </dl>
     1129         </li>
     1130      </ul>
    11251131      <p id="rfc.section.3.2.2.p.5"> <span id="rfc.iref.c.14"></span>  <span id="rfc.iref.n.5"></span> no-store
    11261132      </p>
    1127       <dl class="empty">
    1128          <dd>The no-store response directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both non-shared and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
    1129          </dd>
    1130          <dd>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
     1133      <ul class="empty">
     1134         <li>The no-store response directive indicates that a cache <em class="bcp14">MUST NOT</em> store any part of either the immediate request or response. This directive applies to both non-shared and shared caches. "<em class="bcp14">MUST NOT</em> store" in this context means that the cache <em class="bcp14">MUST NOT</em> intentionally store the information in non-volatile storage, and <em class="bcp14">MUST</em> make a best-effort attempt to remove the information from volatile storage as promptly as possible after forwarding it.
     1135         </li>
     1136         <li>This directive is NOT a reliable or sufficient mechanism for ensuring privacy. In particular, malicious or compromised caches
    11311137            might not recognize or obey this directive, and communications networks may be vulnerable to eavesdropping.
    1132          </dd>
    1133       </dl>
     1138         </li>
     1139      </ul>
    11341140      <p id="rfc.section.3.2.2.p.6"> <span id="rfc.iref.c.15"></span>  <span id="rfc.iref.m.4"></span> must-revalidate
    11351141      </p>
    1136       <dl class="empty">
    1137          <dd>The must-revalidate response directive indicates that once it has become stale, the response <em class="bcp14">MUST NOT</em> be used to satisfy subsequent requests without successful validation on the origin server.
    1138          </dd>
    1139          <dd>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
     1142      <ul class="empty">
     1143         <li>The must-revalidate response directive indicates that once it has become stale, the response <em class="bcp14">MUST NOT</em> be used to satisfy subsequent requests without successful validation on the origin server.
     1144         </li>
     1145         <li>The must-revalidate directive is necessary to support reliable operation for certain protocol features. In all circumstances
    11401146            an HTTP/1.1 cache <em class="bcp14">MUST</em> obey the must-revalidate directive; in particular, if the cache cannot reach the origin server for any reason, it <em class="bcp14">MUST</em> generate a 504 (Gateway Timeout) response.
    1141          </dd>
    1142          <dd>Servers <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to validate a request on the entity could result in incorrect operation,
     1147         </li>
     1148         <li>Servers <em class="bcp14">SHOULD</em> send the must-revalidate directive if and only if failure to validate a request on the entity could result in incorrect operation,
    11431149            such as a silently unexecuted financial transaction.
    1144          </dd>
    1145       </dl>
     1150         </li>
     1151      </ul>
    11461152      <p id="rfc.section.3.2.2.p.7"> <span id="rfc.iref.c.16"></span>  <span id="rfc.iref.p.3"></span> proxy-revalidate
    11471153      </p>
    1148       <dl class="empty">
    1149          <dd>The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does
     1154      <ul class="empty">
     1155         <li>The proxy-revalidate response directive has the same meaning as the must-revalidate response directive, except that it does
    11501156            not apply to non-shared caches.
    1151          </dd>
    1152       </dl>
     1157         </li>
     1158      </ul>
    11531159      <p id="rfc.section.3.2.2.p.8"> <span id="rfc.iref.c.17"></span>  <span id="rfc.iref.m.5"></span> max-age
    11541160      </p>
    1155       <dl class="empty">
    1156          <dd>The max-age response directive indicates that response is to be considered stale after its age is greater than the specified
     1161      <ul class="empty">
     1162         <li>The max-age response directive indicates that response is to be considered stale after its age is greater than the specified
    11571163            number of seconds.
    1158          </dd>
    1159       </dl>
     1164         </li>
     1165      </ul>
    11601166      <p id="rfc.section.3.2.2.p.9"> <span id="rfc.iref.c.18"></span>  <span id="rfc.iref.s.2"></span> s-maxage
    11611167      </p>
    1162       <dl class="empty">
    1163          <dd>The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the
     1168      <ul class="empty">
     1169         <li>The s-maxage response directive indicates that, in shared caches, the maximum age specified by this directive overrides the
    11641170            maximum age specified by either the max-age directive or the Expires header. The s-maxage directive also implies the semantics
    11651171            of the proxy-revalidate response directive.
    1166          </dd>
    1167       </dl>
     1172         </li>
     1173      </ul>
    11681174      <p id="rfc.section.3.2.2.p.10"> <span id="rfc.iref.c.19"></span>  <span id="rfc.iref.n.6"></span> no-transform
    11691175      </p>
    1170       <dl class="empty">
    1171          <dd>The no-transform response directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type response headers, nor the response entity-body.
    1172          </dd>
    1173       </dl>
     1176      <ul class="empty">
     1177         <li>The no-transform response directive indicates that an intermediate cache or proxy <em class="bcp14">MUST NOT</em> change the Content-Encoding, Content-Range or Content-Type response headers, nor the response entity-body.
     1178         </li>
     1179      </ul>
    11741180      <h3 id="rfc.section.3.2.3"><a href="#rfc.section.3.2.3">3.2.3</a>&nbsp;<a id="cache.control.extensions" href="#cache.control.extensions">Cache Control Extensions</a></h3>
    11751181      <p id="rfc.section.3.2.3.p.1">The Cache-Control header field can be extended through the use of one or more cache-extension tokens, each with an optional
     
    13171323      </p>
    13181324      <p id="rfc.section.3.6.p.12"> 110 Response is stale </p>
    1319       <dl class="empty">
    1320          <dd><em class="bcp14">SHOULD</em> be included whenever the returned response is stale.
    1321          </dd>
    1322       </dl>
     1325      <ul class="empty">
     1326         <li><em class="bcp14">SHOULD</em> be included whenever the returned response is stale.
     1327         </li>
     1328      </ul>
    13231329      <p id="rfc.section.3.6.p.13"> 111 Revalidation failed </p>
    1324       <dl class="empty">
    1325          <dd><em class="bcp14">SHOULD</em> be included if a cache returns a stale response because an attempt to validate the response failed, due to an inability to
     1330      <ul class="empty">
     1331         <li><em class="bcp14">SHOULD</em> be included if a cache returns a stale response because an attempt to validate the response failed, due to an inability to
    13261332            reach the server.
    1327          </dd>
    1328       </dl>
     1333         </li>
     1334      </ul>
    13291335      <p id="rfc.section.3.6.p.14"> 112 Disconnected operation </p>
    1330       <dl class="empty">
    1331          <dd><em class="bcp14">SHOULD</em> be included if the cache is intentionally disconnected from the rest of the network for a period of time.
    1332          </dd>
    1333       </dl>
     1336      <ul class="empty">
     1337         <li><em class="bcp14">SHOULD</em> be included if the cache is intentionally disconnected from the rest of the network for a period of time.
     1338         </li>
     1339      </ul>
    13341340      <p id="rfc.section.3.6.p.15"> 113 Heuristic expiration </p>
    1335       <dl class="empty">
    1336          <dd><em class="bcp14">SHOULD</em> be included if the cache heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater
     1341      <ul class="empty">
     1342         <li><em class="bcp14">SHOULD</em> be included if the cache heuristically chose a freshness lifetime greater than 24 hours and the response's age is greater
    13371343            than 24 hours.
    1338          </dd>
    1339       </dl>
     1344         </li>
     1345      </ul>
    13401346      <p id="rfc.section.3.6.p.16"> 199 Miscellaneous warning </p>
    1341       <dl class="empty">
    1342          <dd>The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action, besides presenting the warning to the user.
    1343          </dd>
    1344       </dl>
     1347      <ul class="empty">
     1348         <li>The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action, besides presenting the warning to the user.
     1349         </li>
     1350      </ul>
    13451351      <p id="rfc.section.3.6.p.17"> 214 Transformation applied </p>
    1346       <dl class="empty">
    1347          <dd><em class="bcp14">MUST</em> be added by an intermediate cache or proxy if it applies any transformation changing the content-coding (as specified in the
     1352      <ul class="empty">
     1353         <li><em class="bcp14">MUST</em> be added by an intermediate cache or proxy if it applies any transformation changing the content-coding (as specified in the
    13481354            Content-Encoding header) or media-type (as specified in the Content-Type header) of the response, or the entity-body of the
    13491355            response, unless this Warning code already appears in the response.
    1350          </dd>
    1351       </dl>
     1356         </li>
     1357      </ul>
    13521358      <p id="rfc.section.3.6.p.18"> 299 Miscellaneous persistent warning </p>
    1353       <dl class="empty">
    1354          <dd>The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action.
    1355          </dd>
    1356       </dl>
     1359      <ul class="empty">
     1360         <li>The warning text can include arbitrary information to be presented to a human user, or logged. A system receiving this warning <em class="bcp14">MUST NOT</em> take any automated action.
     1361         </li>
     1362      </ul>
    13571363      <h1 id="rfc.section.4"><a href="#rfc.section.4">4.</a>&nbsp;<a id="history.lists" href="#history.lists">History Lists</a></h1>
    13581364      <p id="rfc.section.4.p.1">User agents often have history mechanisms, such as "Back" buttons and history lists, that can be used to redisplay an entity
     
    14541460         <tr>
    14551461            <td class="reference"><b id="Part1">[Part1]</b></td>
    1456             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), November&nbsp;2009.
     1462            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p1-messaging-latest">HTTP/1.1, part 1: URIs, Connections, and Message Parsing</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p1-messaging-latest (work in progress), December&nbsp;2009.
    14571463            </td>
    14581464         </tr>
    14591465         <tr>
    14601466            <td class="reference"><b id="Part2">[Part2]</b></td>
    1461             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), November&nbsp;2009.
     1467            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p2-semantics-latest">HTTP/1.1, part 2: Message Semantics</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p2-semantics-latest (work in progress), December&nbsp;2009.
    14621468            </td>
    14631469         </tr>
    14641470         <tr>
    14651471            <td class="reference"><b id="Part3">[Part3]</b></td>
    1466             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-latest (work in progress), November&nbsp;2009.
     1472            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p3-payload-latest">HTTP/1.1, part 3: Message Payload and Content Negotiation</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p3-payload-latest (work in progress), December&nbsp;2009.
    14671473            </td>
    14681474         </tr>
    14691475         <tr>
    14701476            <td class="reference"><b id="Part4">[Part4]</b></td>
    1471             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), November&nbsp;2009.
     1477            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p4-conditional-latest">HTTP/1.1, part 4: Conditional Requests</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p4-conditional-latest (work in progress), December&nbsp;2009.
    14721478            </td>
    14731479         </tr>
    14741480         <tr>
    14751481            <td class="reference"><b id="Part5">[Part5]</b></td>
    1476             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), November&nbsp;2009.
     1482            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p5-range-latest">HTTP/1.1, part 5: Range Requests and Partial Responses</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p5-range-latest (work in progress), December&nbsp;2009.
    14771483            </td>
    14781484         </tr>
    14791485         <tr>
    14801486            <td class="reference"><b id="Part7">[Part7]</b></td>
    1481             <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), November&nbsp;2009.
     1487            <td class="top"><a href="mailto:fielding@gbiv.com" title="Day Software">Fielding, R., Ed.</a>, <a href="mailto:jg@laptop.org" title="One Laptop per Child">Gettys, J.</a>, <a href="mailto:JeffMogul@acm.org" title="Hewlett-Packard Company">Mogul, J.</a>, <a href="mailto:henrikn@microsoft.com" title="Microsoft Corporation">Frystyk, H.</a>, <a href="mailto:LMM@acm.org" title="Adobe Systems, Incorporated">Masinter, L.</a>, <a href="mailto:paulle@microsoft.com" title="Microsoft Corporation">Leach, P.</a>, <a href="mailto:timbl@w3.org" title="World Wide Web Consortium">Berners-Lee, T.</a>, <a href="mailto:ylafon@w3.org" title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a href="mailto:julian.reschke@greenbytes.de" title="greenbytes GmbH">J. F. Reschke, Ed.</a>, “<a href="http://tools.ietf.org/html/draft-ietf-httpbis-p7-auth-latest">HTTP/1.1, part 7: Authentication</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p7-auth-latest (work in progress), December&nbsp;2009.
    14821488            </td>
    14831489         </tr>
Note: See TracChangeset for help on using the changeset viewer.