Ignore:
Timestamp:
Aug 5, 2008, 1:36:29 PM (11 years ago)
Author:
julian.reschke@…
Message:

Resolve #126: use current Date header reference instead of pointing to RFC2068 (closes #126).

File:
1 edited

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/p4-conditional.html

    r305 r306  
    612612      <ul>
    613613         <li>
    614             <p>Date, unless its omission is required by <a href="p1-messaging.html#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section 8.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a></p>
     614            <p>Date, unless its omission is required by <a href="p1-messaging.html#clockless.origin.server.operation" title="Clockless Origin Server Operation">Section 8.3.1</a> of <a href="#Part1" id="rfc.xref.Part1.5"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     615            </p>
    615616            <p>If a clockless origin server obeys these rules, and proxies and clients add their own Date to any response received without
    616                one (as already specified by <a href="#RFC2068" id="rfc.xref.RFC2068.1"><cite title="Hypertext Transfer Protocol -- HTTP/1.1">[RFC2068]</cite></a>, <a href="http://tools.ietf.org/html/rfc2068#section-14.19">Section 14.19</a>), caches will operate correctly.
     617               one (as already specified by <a href="p1-messaging.html#header.date" title="Date">Section 8.3</a> of <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>, caches will operate correctly.
    617618            </p>
    618619         </li>
    619620         <li>
    620             <p>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request</p>
     621            <p>ETag and/or Content-Location, if the header would have been sent in a 200 response to the same request.</p>
    621622         </li>
    622623         <li>
    623624            <p>Expires, Cache-Control, and/or Vary, if the field-value might differ from that sent in any previous response for the same
    624                variant
     625               variant.
    625626            </p>
    626627         </li>
     
    10641065      <p id="rfc.section.8.1.p.2">The change controller is: "IETF (iesg@ietf.org) - Internet Engineering Task Force".</p>
    10651066      <h1 id="rfc.section.9"><a href="#rfc.section.9">9.</a>&nbsp;<a id="security.considerations" href="#security.considerations">Security Considerations</a></h1>
    1066       <p id="rfc.section.9.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.6"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
     1067      <p id="rfc.section.9.p.1">No additional security considerations have been identified beyond those applicable to HTTP in general <a href="#Part1" id="rfc.xref.Part1.7"><cite title="HTTP/1.1, part 1: URIs, Connections, and Message Parsing">[Part1]</cite></a>.
    10671068      </p>
    10681069      <h1 id="rfc.section.10"><a href="#rfc.section.10">10.</a>&nbsp;<a id="ack" href="#ack">Acknowledgments</a></h1>
     
    10951096      <h2 id="rfc.references.2"><a href="#rfc.section.11.2" id="rfc.section.11.2">11.2</a> Informative References
    10961097      </h2>
    1097       <table summary="Informative References">     
    1098          <tr>
    1099             <td class="reference"><b id="RFC2068">[RFC2068]</b></td>
    1100             <td class="top"><a title="University of California, Irvine, Department of Information and Computer Science">Fielding, R.</a>, <a title="MIT Laboratory for Computer Science">Gettys, J.</a>, <a title="Digital Equipment Corporation, Western Research Laboratory">Mogul, J.</a>, <a title="MIT Laboratory for Computer Science">Nielsen, H.</a>, and <a title="MIT Laboratory for Computer Science">T. Berners-Lee</a>, “<a href="http://tools.ietf.org/html/rfc2068">Hypertext Transfer Protocol -- HTTP/1.1</a>”, RFC&nbsp;2068, January&nbsp;1997.
    1101             </td>
    1102          </tr>
     1098      <table summary="Informative References">   
    11031099         <tr>
    11041100            <td class="reference"><b id="RFC2616">[RFC2616]</b></td>
     
    11721168         </li>
    11731169         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/124">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/124</a>&gt;: "'entity value' undefined"
     1170         </li>
     1171         <li> &lt;<a href="http://www3.tools.ietf.org/wg/httpbis/trac/ticket/126">http://www3.tools.ietf.org/wg/httpbis/trac/ticket/126</a>&gt;: "bogus 2068 Date header reference"
    11741172         </li>
    11751173      </ul>
     
    12561254            </li>
    12571255            <li class="indline0"><a id="rfc.index.P" href="#rfc.index.P"><b>P</b></a><ul class="ind">
    1258                   <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">4.1</a>, <a class="iref" href="#rfc.xref.Part1.6">9</a>, <a class="iref" href="#Part1"><b>11.1</b></a><ul class="ind">
     1256                  <li class="indline1"><em>Part1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a>, <a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a>, <a class="iref" href="#rfc.xref.Part1.4">2</a>, <a class="iref" href="#rfc.xref.Part1.5">4.1</a>, <a class="iref" href="#rfc.xref.Part1.6">4.1</a>, <a class="iref" href="#rfc.xref.Part1.7">9</a>, <a class="iref" href="#Part1"><b>11.1</b></a><ul class="ind">
    12591257                        <li class="indline1"><em>Section 2.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.1">2</a></li>
    12601258                        <li class="indline1"><em>Section 2.2</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.2">2</a>, <a class="iref" href="#rfc.xref.Part1.3">2</a></li>
    12611259                        <li class="indline1"><em>Section 3.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.4">2</a></li>
    12621260                        <li class="indline1"><em>Section 8.3.1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.5">4.1</a></li>
     1261                        <li class="indline1"><em>Section 8.3</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.Part1.6">4.1</a></li>
    12631262                     </ul>
    12641263                  </li>
     
    12751274            </li>
    12761275            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    1277                   <li class="indline1"><em>RFC2068</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">4.1</a>, <a class="iref" href="#RFC2068"><b>11.2</b></a><ul class="ind">
    1278                         <li class="indline1"><em>Section 14.19</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2068.1">4.1</a></li>
    1279                      </ul>
    1280                   </li>
    12811276                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.1</a>, <a class="iref" href="#RFC2119"><b>11.1</b></a></li>
    12821277                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2616.1">1</a>, <a class="iref" href="#RFC2616"><b>11.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.2">B.1</a></li>
Note: See TracChangeset for help on using the changeset viewer.