Ignore:
Timestamp:
13/09/13 09:50:28 (7 years ago)
Author:
fielding@…
Message:

Revert [2368] that attempted to address #486 because it adds incompatible requirements to HTTP/1.1 senders of Warning

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

Legend:

Unmodified
Added
Removed
  • draft-ietf-httpbis/latest/httpbis.abnf

    r2380 r2382  
    227227warn-date = DQUOTE HTTP-date DQUOTE
    228228warn-text = quoted-string
    229 warning-value = warn-code SP warn-agent SP warn-text SP warn-date
     229warning-value = warn-code SP warn-agent SP warn-text [ SP warn-date ]
    230230weak = %x57.2F ; W/
    231231
  • draft-ietf-httpbis/latest/p6-cache.html

    r2372 r2382  
    449449  }
    450450  @bottom-center {
    451        content: "Expires March 11, 2014";
     451       content: "Expires March 17, 2014";
    452452  }
    453453  @bottom-right {
     
    493493      <meta name="dct.creator" content="Reschke, J. F.">
    494494      <meta name="dct.identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    495       <meta name="dct.issued" scheme="ISO8601" content="2013-09-07">
     495      <meta name="dct.issued" scheme="ISO8601" content="2013-09-13">
    496496      <meta name="dct.replaces" content="urn:ietf:rfc:2616">
    497497      <meta name="dct.abstract" content="The Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypertext information systems. This document defines requirements on HTTP caches and the associated header fields that control cache behavior or indicate cacheable response messages.">
     
    519519            </tr>
    520520            <tr>
    521                <td class="left">Expires: March 11, 2014</td>
     521               <td class="left">Expires: March 17, 2014</td>
    522522               <td class="right">J. Reschke, Editor</td>
    523523            </tr>
     
    528528            <tr>
    529529               <td class="left"></td>
    530                <td class="right">September 7, 2013</td>
     530               <td class="right">September 13, 2013</td>
    531531            </tr>
    532532         </tbody>
     
    554554         in progress”.
    555555      </p>
    556       <p>This Internet-Draft will expire on March 11, 2014.</p>
     556      <p>This Internet-Draft will expire on March 17, 2014.</p>
    557557      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    558558      <p>Copyright © 2013 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
     
    14651465 
    14661466  <a href="#header.warning" class="smpl">warning-value</a> = <a href="#header.warning" class="smpl">warn-code</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-agent</a> <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-text</a>
    1467                                           <a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a>
     1467                                        [<a href="#imported.abnf" class="smpl">SP</a> <a href="#header.warning" class="smpl">warn-date</a>]
    14681468 
    14691469  <a href="#header.warning" class="smpl">warn-code</a>  = 3<a href="#imported.abnf" class="smpl">DIGIT</a>
     
    14911491         </li>
    14921492      </ul>
    1493       <p id="rfc.section.5.5.p.9">HTTP/1.0 caches will cache all Warnings in responses, without deleting the ones in the first category. Thus, Warnings in responses
    1494          carry a warning-date field, which can help in detecting an erroneously cached Warning.
    1495       </p>
    1496       <p id="rfc.section.5.5.p.10">RFC 2616 made the Warning header field's warn-date component optional; it was only required to be sent when the recipient's
    1497          version was HTTP/1.0 or lower. However, deployment experience has shown that many intermediaries do not process the Warning
    1498          header field as required by RFC 2616. This results in situations where the field can appear in messages where it is not applicable,
    1499          because a warning-value has not been removed by an intermediary.
    1500       </p>
    1501       <p id="rfc.section.5.5.p.11">As a result, this specification shifts responsibility for processing of Warning from intermediaries to the recipient that
    1502          is actually consuming them.
    1503       </p>
    1504       <p id="rfc.section.5.5.p.12">Generators of Warning header fields <em class="bcp14">MUST</em> include in every warning-value a warn-date that matches the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field in the message. Recipients that process a Warning header field <em class="bcp14">MUST</em> ignore (and <em class="bcp14">MAY</em> remove before forwarding) a warning-value whose warn-date is different from the Date value in the response.
    1505       </p>
    1506       <p id="rfc.section.5.5.p.13">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description
     1493      <p id="rfc.section.5.5.p.9">If an implementation sends a message with one or more Warning header fields to a receiver whose version is HTTP/1.0 or lower,
     1494         then the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the <a href="p2-semantics.html#header.date" class="smpl">Date</a> header field in the message.
     1495      </p>
     1496      <p id="rfc.section.5.5.p.10">If a system receives a message with a warning-value that includes a warn-date, and that warn-date is different from the <a href="p2-semantics.html#header.date" class="smpl">Date</a> value in the response, then that warning-value <em class="bcp14">MUST</em> be deleted from the message before storing, forwarding, or using it (preventing the consequences of naive caching of Warning
     1497         header fields). If all of the warning-values are deleted for this reason, the Warning header field <em class="bcp14">MUST</em> be deleted as well.
     1498      </p>
     1499      <p id="rfc.section.5.5.p.11">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description
    15071500         of its meaning.
    15081501      </p>
     
    19361929      <p id="rfc.section.A.p.14">The <a href="#header.pragma" class="smpl">Pragma</a> header field is now only defined for backwards compatibility; future pragmas are deprecated. (<a href="#header.pragma" id="rfc.xref.header.pragma.3" title="Pragma">Section&nbsp;5.4</a>)
    19371930      </p>
    1938       <p id="rfc.section.A.p.15">Some requirements regarding production of the <a href="#header.warning" class="smpl">Warning</a> header fields have been relaxed, as it is not widely implemented. Furthermore, presence of the warn-date component has been
    1939          made required (dropping requirements specific to HTTP/1.0). Finally, the <a href="#header.warning" class="smpl">Warning</a> header field no longer uses RFC 2047 encoding, nor allows multiple languages, as these aspects were not implemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section&nbsp;5.5</a>)
     1931      <p id="rfc.section.A.p.15">Some requirements regarding production of the <a href="#header.warning" class="smpl">Warning</a> header fields have been relaxed, as it is not widely implemented. Furthermore, the <a href="#header.warning" class="smpl">Warning</a> header field no longer uses RFC 2047 encoding, nor allows multiple languages, as these aspects were not implemented. (<a href="#header.warning" id="rfc.xref.header.warning.6" title="Warning">Section&nbsp;5.5</a>)
    19401932      </p>
    19411933      <p id="rfc.section.A.p.16">This specification introduces the Cache Directive and Warn Code Registries, and defines considerations for new cache directives.
     
    20011993<a href="#header.warning" class="smpl">warn-date</a> = DQUOTE HTTP-date DQUOTE
    20021994<a href="#header.warning" class="smpl">warn-text</a> = quoted-string
    2003 <a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text SP warn-date
     1995<a href="#header.warning" class="smpl">warning-value</a> = warn-code SP warn-agent SP warn-text [ SP warn-date
     1996 ]
    20041997</pre><h1 id="rfc.section.D"><a href="#rfc.section.D">D.</a>&nbsp;<a id="change.log" href="#change.log">Change Log (to be removed by RFC Editor before publication)</a></h1>
    20051998      <p id="rfc.section.D.p.1">Changes up to the first Working Group Last Call draft are summarized in &lt;<a href="http://trac.tools.ietf.org/html/draft-ietf-httpbis-p6-cache-19#appendix-C">http://trac.tools.ietf.org/html/draft-ietf-httpbis-p6-cache-19#appendix-C</a>&gt;.
     
    20642057      </ul>
    20652058      <h2 id="rfc.section.D.5"><a href="#rfc.section.D.5">D.5</a>&nbsp;<a id="changes.since.23" href="#changes.since.23">Since draft-ietf-httpbis-p6-cache-23</a></h2>
    2066       <p id="rfc.section.D.5.p.1">Closed issues: </p>
    2067       <ul>
    2068          <li>&lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/486">http://tools.ietf.org/wg/httpbis/trac/ticket/486</a>&gt;: "Requiring proxies to process warn-date"
    2069          </li>
    2070       </ul>
     2059      <p id="rfc.section.D.5.p.1">None yet.</p>
    20712060      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    20722061      <p class="noprint"><a href="#rfc.index.1">1</a> <a href="#rfc.index.2">2</a> <a href="#rfc.index.A">A</a> <a href="#rfc.index.B">B</a> <a href="#rfc.index.C">C</a> <a href="#rfc.index.E">E</a> <a href="#rfc.index.F">F</a> <a href="#rfc.index.G">G</a> <a href="#rfc.index.H">H</a> <a href="#rfc.index.M">M</a> <a href="#rfc.index.N">N</a> <a href="#rfc.index.O">O</a> <a href="#rfc.index.P">P</a> <a href="#rfc.index.R">R</a> <a href="#rfc.index.S">S</a> <a href="#rfc.index.V">V</a> <a href="#rfc.index.W">W</a>
  • draft-ietf-httpbis/latest/p6-cache.xml

    r2372 r2382  
    17541754 
    17551755  <x:ref>warning-value</x:ref> = <x:ref>warn-code</x:ref> <x:ref>SP</x:ref> <x:ref>warn-agent</x:ref> <x:ref>SP</x:ref> <x:ref>warn-text</x:ref>
    1756                                           <x:ref>SP</x:ref> <x:ref>warn-date</x:ref>
     1756                                        [<x:ref>SP</x:ref> <x:ref>warn-date</x:ref>]
    17571757 
    17581758  <x:ref>warn-code</x:ref>  = 3<x:ref>DIGIT</x:ref>
     
    17931793</t>
    17941794<t>
    1795    HTTP/1.0 caches will cache all Warnings in responses, without deleting the
    1796    ones in the first category. Thus, Warnings in responses carry a warning-date
    1797    field, which can help in detecting an erroneously cached Warning.
    1798 </t>
    1799 <t>
    1800    RFC 2616 made the Warning header field's warn-date component optional; it
    1801    was only required to be sent when the recipient's version was HTTP/1.0 or lower.
    1802    However, deployment experience has shown that many intermediaries
    1803    do not process the Warning header field as required by RFC 2616. This results in
    1804    situations where the field can appear in messages where it is not applicable, because
    1805    a warning-value has not been removed by an intermediary.
    1806 </t>
    1807 <t>
    1808    As a result, this specification shifts responsibility for processing of Warning from
    1809    intermediaries to the recipient that is actually consuming them.
    1810 </t>
    1811 <t>
    1812    Generators of Warning header fields &MUST; include in every warning-value
    1813    a warn-date that matches the <x:ref>Date</x:ref> header field in the message. Recipients that
    1814    process a Warning header field &MUST; ignore (and &MAY; remove before forwarding)
    1815    a warning-value whose warn-date is different from the Date value in the response.
     1795   If an implementation sends a message with one or more Warning header fields
     1796   to a receiver whose version is HTTP/1.0 or lower, then the sender &MUST;
     1797   include in each warning-value a warn-date that matches the
     1798   <x:ref>Date</x:ref> header field in the message.
     1799</t>
     1800<t>
     1801   If a system receives a message with a warning-value that includes a
     1802   warn-date, and that warn-date is different from the <x:ref>Date</x:ref>
     1803   value in the response, then that warning-value &MUST; be deleted from the
     1804   message before storing, forwarding, or using it (preventing the
     1805   consequences of naive caching of Warning header fields). If all of the
     1806   warning-values are deleted for this reason, the Warning header field &MUST;
     1807   be deleted as well.
    18161808</t>
    18171809<t>
     
    25672559  Some requirements regarding production of the <x:ref>Warning</x:ref>
    25682560  header fields have been relaxed, as it is not widely implemented.
    2569   Furthermore, presence of the warn-date component has been made required
    2570   (dropping requirements specific to HTTP/1.0). Finally, the
    2571   <x:ref>Warning</x:ref> header field no longer uses RFC 2047 encoding,
     2561  Furthermore, the <x:ref>Warning</x:ref> header field no longer uses RFC 2047 encoding,
    25722562  nor allows multiple languages, as these aspects were not implemented.
    25732563  (<xref target="header.warning" />)
     
    26702660<x:ref>warn-date</x:ref> = DQUOTE HTTP-date DQUOTE
    26712661<x:ref>warn-text</x:ref> = quoted-string
    2672 <x:ref>warning-value</x:ref> = warn-code SP warn-agent SP warn-text SP warn-date
     2662<x:ref>warning-value</x:ref> = warn-code SP warn-agent SP warn-text [ SP warn-date
     2663 ]
    26732664</artwork>
    26742665</figure>
     
    28052796<section title="Since draft-ietf-httpbis-p6-cache-23" anchor="changes.since.23">
    28062797<t>
    2807   Closed issues:
    2808   <list style="symbols">
    2809     <t>
    2810       <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/486"/>:
    2811       "Requiring proxies to process warn-date"
    2812     </t>
    2813   </list>
     2798   None yet.
    28142799</t>
    28152800</section>
Note: See TracChangeset for help on using the changeset viewer.