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/p4-conditional.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}
     
    167170
    168171table.header {
     172  border-spacing: 1px;
    169173  width: 95%;
    170174  font-size: 10pt;
     
    178182  white-space: nowrap;
    179183}
    180 td.header {
     184table.header td {
    181185  background-color: gray;
    182186  width: 50%;
    183187}
    184 td.header a {
     188table.header a {
    185189  color: white;
    186190}
     
    340344  }
    341345  @top-right {
    342        content: "November 2009";
     346       content: "December 2009";
    343347  }
    344348  @top-center {
     
    384388      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    385389      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    386       <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/">
     390      <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/">
    387391      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    388392      <meta name="DC.Creator" content="Fielding, R.">
     
    396400      <meta name="DC.Creator" content="Reschke, J. F.">
    397401      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p4-conditional-latest">
    398       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-11-27">
     402      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-12-01">
    399403      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    400404      <meta name="DC.Description.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.">
     
    402406   </head>
    403407   <body>
    404       <table class="header" border="0" cellpadding="1" cellspacing="1">
    405          <tr>
    406             <td class="header left">HTTPbis Working Group</td>
    407             <td class="header right">R. Fielding, Editor</td>
    408          </tr>
    409          <tr>
    410             <td class="header left">Internet Draft</td>
    411             <td class="header right">Day Software</td>
    412          </tr>
    413          <tr>
    414             <td class="header left">
    415                &lt;draft-ietf-httpbis-p4-conditional-latest&gt;
    416                
    417             </td>
    418             <td class="header right">J. Gettys</td>
    419          </tr>
    420          <tr>
    421             <td class="header left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
    422             </td>
    423             <td class="header right">One Laptop per Child</td>
    424          </tr>
    425          <tr>
    426             <td class="header left">Intended status: Standards Track</td>
    427             <td class="header right">J. Mogul</td>
    428          </tr>
    429          <tr>
    430             <td class="header left">Expires: May 31, 2010</td>
    431             <td class="header right">HP</td>
    432          </tr>
    433          <tr>
    434             <td class="header left"></td>
    435             <td class="header right">H. Frystyk</td>
    436          </tr>
    437          <tr>
    438             <td class="header left"></td>
    439             <td class="header right">Microsoft</td>
    440          </tr>
    441          <tr>
    442             <td class="header left"></td>
    443             <td class="header right">L. Masinter</td>
    444          </tr>
    445          <tr>
    446             <td class="header left"></td>
    447             <td class="header right">Adobe Systems</td>
    448          </tr>
    449          <tr>
    450             <td class="header left"></td>
    451             <td class="header right">P. Leach</td>
    452          </tr>
    453          <tr>
    454             <td class="header left"></td>
    455             <td class="header right">Microsoft</td>
    456          </tr>
    457          <tr>
    458             <td class="header left"></td>
    459             <td class="header right">T. Berners-Lee</td>
    460          </tr>
    461          <tr>
    462             <td class="header left"></td>
    463             <td class="header right">W3C/MIT</td>
    464          </tr>
    465          <tr>
    466             <td class="header left"></td>
    467             <td class="header right">Y. Lafon, Editor</td>
    468          </tr>
    469          <tr>
    470             <td class="header left"></td>
    471             <td class="header right">W3C</td>
    472          </tr>
    473          <tr>
    474             <td class="header left"></td>
    475             <td class="header right">J. F. Reschke, Editor</td>
    476          </tr>
    477          <tr>
    478             <td class="header left"></td>
    479             <td class="header right">greenbytes</td>
    480          </tr>
    481          <tr>
    482             <td class="header left"></td>
    483             <td class="header right">November 27, 2009</td>
    484          </tr>
     408      <table class="header">
     409         <tbody>
     410            <tr>
     411               <td class="left">HTTPbis Working Group</td>
     412               <td class="right">R. Fielding, Editor</td>
     413            </tr>
     414            <tr>
     415               <td class="left">Internet Draft</td>
     416               <td class="right">Day Software</td>
     417            </tr>
     418            <tr>
     419               <td class="left">
     420                  &lt;draft-ietf-httpbis-p4-conditional-latest&gt;
     421                 
     422               </td>
     423               <td class="right">J. Gettys</td>
     424            </tr>
     425            <tr>
     426               <td class="left">Obsoletes: <a href="http://tools.ietf.org/html/rfc2616">2616</a> (if approved)
     427               </td>
     428               <td class="right">One Laptop per Child</td>
     429            </tr>
     430            <tr>
     431               <td class="left">Intended status: Standards Track</td>
     432               <td class="right">J. Mogul</td>
     433            </tr>
     434            <tr>
     435               <td class="left">Expires: June 4, 2010</td>
     436               <td class="right">HP</td>
     437            </tr>
     438            <tr>
     439               <td class="left"></td>
     440               <td class="right">H. Frystyk</td>
     441            </tr>
     442            <tr>
     443               <td class="left"></td>
     444               <td class="right">Microsoft</td>
     445            </tr>
     446            <tr>
     447               <td class="left"></td>
     448               <td class="right">L. Masinter</td>
     449            </tr>
     450            <tr>
     451               <td class="left"></td>
     452               <td class="right">Adobe Systems</td>
     453            </tr>
     454            <tr>
     455               <td class="left"></td>
     456               <td class="right">P. Leach</td>
     457            </tr>
     458            <tr>
     459               <td class="left"></td>
     460               <td class="right">Microsoft</td>
     461            </tr>
     462            <tr>
     463               <td class="left"></td>
     464               <td class="right">T. Berners-Lee</td>
     465            </tr>
     466            <tr>
     467               <td class="left"></td>
     468               <td class="right">W3C/MIT</td>
     469            </tr>
     470            <tr>
     471               <td class="left"></td>
     472               <td class="right">Y. Lafon, Editor</td>
     473            </tr>
     474            <tr>
     475               <td class="left"></td>
     476               <td class="right">W3C</td>
     477            </tr>
     478            <tr>
     479               <td class="left"></td>
     480               <td class="right">J. F. Reschke, Editor</td>
     481            </tr>
     482            <tr>
     483               <td class="left"></td>
     484               <td class="right">greenbytes</td>
     485            </tr>
     486            <tr>
     487               <td class="left"></td>
     488               <td class="right">December 1, 2009</td>
     489            </tr>
     490         </tbody>
    485491      </table>
    486492      <p class="title">HTTP/1.1, part 4: Conditional Requests<br><span class="filename">draft-ietf-httpbis-p4-conditional-latest</span></p>
     
    510516      <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;.
    511517      </p>
    512       <p>This Internet-Draft will expire in May 31, 2010.</p>
     518      <p>This Internet-Draft will expire in June 4, 2010.</p>
    513519      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    514520      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    689695         entity, while a weak validator is part of an identifier for a set of semantically equivalent entities.
    690696      </p>
    691       <dl class="empty">
    692          <dd> <b>Note:</b> One example of a strong validator is an integer that is incremented in stable storage every time an entity is changed.
    693          </dd>
    694          <dd>An entity's modification time, if represented with one-second resolution, could be a weak validator, since it is possible
     697      <ul class="empty">
     698         <li> <b>Note:</b> One example of a strong validator is an integer that is incremented in stable storage every time an entity is changed.
     699         </li>
     700         <li>An entity's modification time, if represented with one-second resolution, could be a weak validator, since it is possible
    695701            that the resource might be modified twice during a single second.
    696          </dd>
    697          <dd>Support for weak validators is optional. However, weak validators allow for more efficient caching of equivalent objects;
     702         </li>
     703         <li>Support for weak validators is optional. However, weak validators allow for more efficient caching of equivalent objects;
    698704            for example, a hit counter on a site is probably good enough if it is updated every few days or weeks, and any value during
    699705            that period is likely "good enough" to be equivalent.
    700          </dd>
    701       </dl>
     706         </li>
     707      </ul>
    702708      <p id="rfc.section.4.p.4">A "use" of a validator is either when a client generates a request and includes the validator in a validating header field,
    703709         or when a server compares two validators.
     
    842848         fields in the request.
    843849      </p>
    844       <dl class="empty">
    845          <dd> <b>Note:</b> The general principle behind these rules is that HTTP/1.1 servers and clients should transmit as much non-redundant information
     850      <ul class="empty">
     851         <li> <b>Note:</b> The general principle behind these rules is that HTTP/1.1 servers and clients should transmit as much non-redundant information
    846852            as is available in their responses and requests. HTTP/1.1 systems receiving this information will make the most conservative
    847853            assumptions about the validators they receive.
    848          </dd>
    849          <dd>HTTP/1.0 clients and caches will ignore entity tags. Generally, last-modified values received or used by these systems will
     854         </li>
     855         <li>HTTP/1.0 clients and caches will ignore entity tags. Generally, last-modified values received or used by these systems will
    850856            support transparent and efficient caching, and so HTTP/1.1 origin servers should provide Last-Modified values. In those rare
    851857            cases where the use of a Last-Modified value as a validator by an HTTP/1.0 system could result in a serious problem, then
    852858            HTTP/1.1 origin servers should not provide one.
    853          </dd>
    854       </dl>
     859         </li>
     860      </ul>
    855861      <h1 id="rfc.section.6"><a href="#rfc.section.6">6.</a>&nbsp;<a id="header.fields" href="#header.fields">Header Field Definitions</a></h1>
    856862      <p id="rfc.section.6.p.1">This section defines the syntax and semantics of HTTP/1.1 header fields related to conditional requests.</p>
     
    939945      </ol>
    940946      <p id="rfc.section.6.3.p.6">The purpose of this feature is to allow efficient updates of cached information with a minimum amount of transaction overhead. </p>
    941       <dl class="empty">
    942          <dd> <b>Note:</b> The Range request-header field modifies the meaning of If-Modified-Since; see <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> for full details.
    943          </dd>
    944          <dd> <b>Note:</b> If-Modified-Since times are interpreted by the server, whose clock might not be synchronized with the client.
    945          </dd>
    946          <dd> <b>Note:</b> When handling an If-Modified-Since header field, some servers will use an exact date comparison function, rather than a less-than
     947      <ul class="empty">
     948         <li> <b>Note:</b> The Range request-header field modifies the meaning of If-Modified-Since; see <a href="p5-range.html#header.range" title="Range">Section 5.4</a> of <a href="#Part5" id="rfc.xref.Part5.4"><cite title="HTTP/1.1, part 5: Range Requests and Partial Responses">[Part5]</cite></a> for full details.
     949         </li>
     950         <li> <b>Note:</b> If-Modified-Since times are interpreted by the server, whose clock might not be synchronized with the client.
     951         </li>
     952         <li> <b>Note:</b> When handling an If-Modified-Since header field, some servers will use an exact date comparison function, rather than a less-than
    947953            function, for deciding whether to send a 304 (Not Modified) response. To get best results when sending an If-Modified-Since
    948954            header field for cache validation, clients are advised to use the exact date string received in a previous Last-Modified header
    949955            field whenever possible.
    950          </dd>
    951          <dd> <b>Note:</b> If a client uses an arbitrary date in the If-Modified-Since header instead of a date taken from the Last-Modified header for
     956         </li>
     957         <li> <b>Note:</b> If a client uses an arbitrary date in the If-Modified-Since header instead of a date taken from the Last-Modified header for
    952958            the same request, the client should be aware of the fact that this date is interpreted in the server's understanding of time.
    953959            The client should consider unsynchronized clocks and rounding problems due to the different encodings of time between the
     
    956962            If-Modified-Since date is derived from the client's clock without correction to the server's clock. Corrections for different
    957963            time bases between client and server are at best approximate due to network latency.
    958          </dd>
    959       </dl>
     964         </li>
     965      </ul>
    960966      <p id="rfc.section.6.3.p.7">The result of a request having both an If-Modified-Since header field and either an If-Match or an If-Unmodified-Since header
    961967         fields is undefined by this specification.
     
    11461152         <tr>
    11471153            <td class="reference"><b id="Part1">[Part1]</b></td>
    1148             <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.
     1154            <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.
    11491155            </td>
    11501156         </tr>
    11511157         <tr>
    11521158            <td class="reference"><b id="Part5">[Part5]</b></td>
    1153             <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.
     1159            <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.
    11541160            </td>
    11551161         </tr>
    11561162         <tr>
    11571163            <td class="reference"><b id="Part6">[Part6]</b></td>
    1158             <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>, <a href="mailto:mnot@mnot.net">Nottingham, M., 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-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), November&nbsp;2009.
     1164            <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>, <a href="mailto:mnot@mnot.net">Nottingham, M., 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-p6-cache-latest">HTTP/1.1, part 6: Caching</a>”, Internet-Draft&nbsp;draft-ietf-httpbis-p6-cache-latest (work in progress), December&nbsp;2009.
    11591165            </td>
    11601166         </tr>
Note: See TracChangeset for help on using the changeset viewer.