Ignore:
Timestamp:
07/08/09 05:52:56 (12 years ago)
Author:
julian.reschke@…
Message:

Remove mentions of character encoding and language in description of Warning header (see #187)

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

Legend:

Unmodified
Added
Removed

  • draft-ietf-httpbis/latest/p6-cache.html

    r662 r669  
    151151  border-style: none none inset none;
    152152  border-width: 1px;
     153}
     154table.left {
     155  margin-right: auto;
     156}
     157table.right {
     158  margin-left: auto;
     159}
     160table.center {
     161  margin-left: auto;
     162  margin-right: auto;
    153163}
    154164caption {
    … …  
    375385      <link rel="Appendix" title="B Collected ABNF" href="#rfc.section.B">
    376386      <link rel="Appendix" title="C Change Log (to be removed by RFC Editor before publication)" href="#rfc.section.C">
    377       <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.445, 2009-08-01 14:05:14, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
     387      <meta name="generator" content="http://greenbytes.de/tech/webdav/rfc2629.xslt, Revision 1.447, 2009-08-04 19:54:03, XSLT vendor: SAXON 8.9 from Saxonica http://www.saxonica.com/">
    378388      <link rel="schema.DC" href="http://purl.org/dc/elements/1.1/">
    379389      <meta name="DC.Creator" content="Fielding, R.">
    … …  
    388398      <meta name="DC.Creator" content="Reschke, J. F.">
    389399      <meta name="DC.Identifier" content="urn:ietf:id:draft-ietf-httpbis-p6-cache-latest">
    390       <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08">
     400      <meta name="DC.Date.Issued" scheme="ISO8601" content="2009-08-07">
    391401      <meta name="DC.Relation.Replaces" content="urn:ietf:rfc:2616">
    392402      <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.">
    … …  
    419429         </tr>
    420430         <tr>
    421             <td class="header left">Expires: February 6, 2010</td>
     431            <td class="header left">Expires: February 8, 2010</td>
    422432            <td class="header right">HP</td>
    423433         </tr>
    … …  
    476486         <tr>
    477487            <td class="header left"></td>
    478             <td class="header right">August 5, 2009</td>
     488            <td class="header right">August 7, 2009</td>
    479489         </tr>
    480490      </table>
    … …  
    500510      <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;.
    501511      </p>
    502       <p>This Internet-Draft will expire in February 6, 2010.</p>
     512      <p>This Internet-Draft will expire in February 8, 2010.</p>
    503513      <h1><a id="rfc.copyrightnotice" href="#rfc.copyrightnotice">Copyright Notice</a></h1>
    504514      <p>Copyright © 2009 IETF Trust and the persons identified as the document authors. All rights reserved.</p>
    … …  
    12771287  <a href="#header.warning" class="smpl">warn-date</a>  = <a href="#notation" class="smpl">DQUOTE</a> <a href="#abnf.dependencies" class="smpl">HTTP-date</a> <a href="#notation" class="smpl">DQUOTE</a>
    12781288</pre><p id="rfc.section.3.6.p.5">Multiple warnings can be attached to a response (either by the origin server or by a cache), including multiple warnings with
    1279          the same code number. For example, a server might provide the same warning with texts in both English and Basque.
    1280       </p>
    1281       <p id="rfc.section.3.6.p.6">When this occurs, the user agent <em class="bcp14">SHOULD</em> inform the user of as many of them as possible, in the order that they appear in the response. If it is not possible to inform
    1282          the user of all of the warnings, the user agent <em class="bcp14">SHOULD</em> follow these heuristics:
    1283       </p>
    1284       <ul>
    1285          <li>Warnings that appear early in the response take priority over those appearing later in the response.</li>
    1286          <li>Warnings in the user's preferred character set take priority over warnings in other character sets but with identical warn-codes
    1287             and warn-agents.
    1288          </li>
    1289       </ul>
     1289         the same code number, only differing in warn-text.
     1290      </p>
     1291      <p id="rfc.section.3.6.p.6">When this occurs, the user agent <em class="bcp14">SHOULD</em> inform the user of as many of them as possible, in the order that they appear in the response.
     1292      </p>
    12901293      <p id="rfc.section.3.6.p.7">Systems that generate multiple Warning headers <em class="bcp14">SHOULD</em> order them with this user agent behavior in mind. New Warning headers <em class="bcp14">SHOULD</em> be added after any existing Warning headers.
    12911294      </p>
    … …  
    13001303         </li>
    13011304      </ul>
    1302       <p id="rfc.section.3.6.p.9">The warn-text <em class="bcp14">SHOULD</em> be in a natural language and character set that is most likely to be intelligible to the human user receiving the response.
    1303          This decision can be based on any available knowledge, such as the location of the cache or user, the Accept-Language field
    1304          in a request, the Content-Language field in a response, etc. The default language is English and the default character set
    1305          is ISO-8859-1 (<a href="#ISO-8859-1" id="rfc.xref.ISO-8859-1.1"><cite title="Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1">[ISO-8859-1]</cite></a>).
    1306       </p>
    1307       <p id="rfc.section.3.6.p.10">If a character set other than ISO-8859-1 is used, it <em class="bcp14">MUST</em> be encoded in the warn-text using the method described in <a href="#RFC2047" id="rfc.xref.RFC2047.1"><cite title="MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text">[RFC2047]</cite></a>.
    1308       </p>
    1309       <p id="rfc.section.3.6.p.11">If an implementation sends a message with one or more Warning headers to a receiver whose version is HTTP/1.0 or lower, then
     1305      <p id="rfc.section.3.6.p.9">If an implementation sends a message with one or more Warning headers to a receiver whose version is HTTP/1.0 or lower, then
    13101306         the sender <em class="bcp14">MUST</em> include in each warning-value a warn-date that matches the Date header in the message.
    13111307      </p>
    1312       <p id="rfc.section.3.6.p.12">If an implementation receives a message with a warning-value that includes a warn-date, and that warn-date is different from
     1308      <p id="rfc.section.3.6.p.10">If an implementation receives a message with a warning-value that includes a warn-date, and that warn-date is different from
    13131309         the Date 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
    13141310         header fields.) If all of the warning-values are deleted for this reason, the Warning header <em class="bcp14">MUST</em> be deleted as well.
    13151311      </p>
    1316       <p id="rfc.section.3.6.p.13">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description
     1312      <p id="rfc.section.3.6.p.11">The following warn-codes are defined by this specification, each with a recommended warn-text in English, and a description
    13171313         of its meaning.
    13181314      </p>
    1319       <p id="rfc.section.3.6.p.14"> 110 Response is stale </p>
     1315      <p id="rfc.section.3.6.p.12"> 110 Response is stale </p>
    13201316      <dl class="empty">
    13211317         <dd><em class="bcp14">SHOULD</em> be included whenever the returned response is stale.
    13221318         </dd>
    13231319      </dl>
    1324       <p id="rfc.section.3.6.p.15"> 111 Revalidation failed </p>
     1320      <p id="rfc.section.3.6.p.13"> 111 Revalidation failed </p>
    13251321      <dl class="empty">
    13261322         <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
    … …  
    13281324         </dd>
    13291325      </dl>
    1330       <p id="rfc.section.3.6.p.16"> 112 Disconnected operation </p>
     1326      <p id="rfc.section.3.6.p.14"> 112 Disconnected operation </p>
    13311327      <dl class="empty">
    13321328         <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.
    13331329         </dd>
    13341330      </dl>
    1335       <p id="rfc.section.3.6.p.17"> 113 Heuristic expiration </p>
     1331      <p id="rfc.section.3.6.p.15"> 113 Heuristic expiration </p>
    13361332      <dl class="empty">
    13371333         <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
    … …  
    13391335         </dd>
    13401336      </dl>
    1341       <p id="rfc.section.3.6.p.18"> 199 Miscellaneous warning </p>
     1337      <p id="rfc.section.3.6.p.16"> 199 Miscellaneous warning </p>
    13421338      <dl class="empty">
    13431339         <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.
    13441340         </dd>
    13451341      </dl>
    1346       <p id="rfc.section.3.6.p.19"> 214 Transformation applied </p>
     1342      <p id="rfc.section.3.6.p.17"> 214 Transformation applied </p>
    13471343      <dl class="empty">
    13481344         <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
    … …  
    13511347         </dd>
    13521348      </dl>
    1353       <p id="rfc.section.3.6.p.20"> 299 Miscellaneous persistent warning </p>
     1349      <p id="rfc.section.3.6.p.18"> 299 Miscellaneous persistent warning </p>
    13541350      <dl class="empty">
    13551351         <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.
    … …  
    13821378      <div id="rfc.table.1">
    13831379         <div id="iana.header.registration.table"></div>
    1384          <table class="tt full" cellpadding="3" cellspacing="0">
     1380         <table class="tt full left" cellpadding="3" cellspacing="0">
    13851381            <thead>
    13861382               <tr>
    … …  
    14521448      <h2 id="rfc.references.1"><a href="#rfc.section.8.1" id="rfc.section.8.1">8.1</a> Normative References
    14531449      </h2>
    1454       <table summary="Normative References">                   
    1455          <tr>
    1456             <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td>
    1457             <td class="top">International Organization for Standardization, “Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1”, ISO/IEC&nbsp;8859-1:1998, 1998.</td>
    1458          </tr>
     1450      <table summary="Normative References">               
    14591451         <tr>
    14601452            <td class="reference"><b id="Part1">[Part1]</b></td>
    … …  
    14851477            <td class="reference"><b id="Part7">[Part7]</b></td>
    14861478            <td class="top"><a title="Day Software">Fielding, R., Ed.</a>, <a title="One Laptop per Child">Gettys, J.</a>, <a title="Hewlett-Packard Company">Mogul, J.</a>, <a title="Microsoft Corporation">Frystyk, H.</a>, <a title="Adobe Systems, Incorporated">Masinter, L.</a>, <a title="Microsoft Corporation">Leach, P.</a>, <a title="World Wide Web Consortium">Berners-Lee, T.</a>, <a title="World Wide Web Consortium">Lafon, Y., Ed.</a>, and <a 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), August&nbsp;2009.
    1487             </td>
    1488          </tr>
    1489          <tr>
    1490             <td class="reference"><b id="RFC2047">[RFC2047]</b></td>
    1491             <td class="top"><a title="University of Tennessee">Moore, K.</a>, “<a href="http://tools.ietf.org/html/rfc2047">MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text</a>”, RFC&nbsp;2047, November&nbsp;1996.
    14921479            </td>
    14931480         </tr>
    … …  
    15631550      <p id="rfc.section.A.2.p.1">Clarify denial of service attack avoidance requirement. (<a href="#invalidation.after.updates.or.deletions" title="Request Methods that Invalidate">Section&nbsp;2.5</a>)
    15641551      </p>
     1552      <p id="rfc.section.A.2.p.2">Do not mention RFC 2047 encoding and multiple languages in Warning headers anymore, as these aspects never were implemented.
     1553         (<a href="#header.warning" id="rfc.xref.header.warning.5" title="Warning">Section&nbsp;3.6</a>)
     1554      </p>
    15651555      <h1 id="rfc.section.B"><a href="#rfc.section.B">B.</a>&nbsp;<a id="collected.abnf" href="#collected.abnf">Collected ABNF</a></h1>
    15661556      <div id="rfc.figure.u.18"></div> <pre class="inline"><a href="#header.age" class="smpl">Age</a> = "Age:" OWS Age-v
    … …  
    17281718      </ul>
    17291719      <h2 id="rfc.section.C.9"><a href="#rfc.section.C.9">C.9</a>&nbsp;<a id="changes.since.07" href="#changes.since.07">Since draft-ietf-httpbis-p6-cache-07</a></h2>
    1730       <p id="rfc.section.C.9.p.1">None.</p>
     1720      <p id="rfc.section.C.9.p.1">Closed issues: </p>
     1721      <ul>
     1722         <li> &lt;<a href="http://tools.ietf.org/wg/httpbis/trac/ticket/187">http://tools.ietf.org/wg/httpbis/trac/ticket/187</a>&gt;: "RFC2047 and warn-text"
     1723         </li>
     1724      </ul>
    17311725      <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1>
    1732       <p class="noprint"><a href="#rfc.index.A">A</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.I">I</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>
     1726      <p class="noprint"><a href="#rfc.index.A">A</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>
    17331727      </p>
    17341728      <div class="print2col">
    … …  
    18101804                        <li class="indline1">Pragma&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.pragma.1">2.2</a>, <a class="iref" href="#rfc.xref.header.pragma.2">3.2</a>, <a class="iref" href="#rfc.iref.h.5"><b>3.4</b></a>, <a class="iref" href="#rfc.xref.header.pragma.3">5.1</a></li>
    18111805                        <li class="indline1">Vary&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.vary.1">2.6</a>, <a class="iref" href="#rfc.iref.h.6"><b>3.5</b></a>, <a class="iref" href="#rfc.xref.header.vary.2">5.1</a></li>
    1812                         <li class="indline1">Warning&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.7</a>, <a class="iref" href="#rfc.iref.h.7"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.1</a>, <a class="iref" href="#rfc.xref.header.warning.4">A.1</a></li>
     1806                        <li class="indline1">Warning&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.7</a>, <a class="iref" href="#rfc.iref.h.7"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.1</a>, <a class="iref" href="#rfc.xref.header.warning.4">A.1</a>, <a class="iref" href="#rfc.xref.header.warning.5">A.2</a></li>
    18131807                     </ul>
    18141808                  </li>
    18151809                  <li class="indline1">heuristic expiration time&nbsp;&nbsp;<a class="iref" href="#rfc.iref.h.1">1.2</a></li>
    1816                </ul>
    1817             </li>
    1818             <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind">
    1819                   <li class="indline1"><em>ISO-8859-1</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.ISO-8859-1.1">3.6</a>, <a class="iref" href="#ISO-8859-1"><b>8.1</b></a></li>
    18201810               </ul>
    18211811            </li>
    … …  
    19181908            <li class="indline0"><a id="rfc.index.R" href="#rfc.index.R"><b>R</b></a><ul class="ind">
    19191909                  <li class="indline1"><em>RFC1305</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC1305.1">2.3.2</a>, <a class="iref" href="#RFC1305"><b>8.2</b></a></li>
    1920                   <li class="indline1"><em>RFC2047</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2047.1">3.6</a>, <a class="iref" href="#RFC2047"><b>8.1</b></a></li>
    19211910                  <li class="indline1"><em>RFC2119</em>&nbsp;&nbsp;<a class="iref" href="#rfc.xref.RFC2119.1">1.3</a>, <a class="iref" href="#RFC2119"><b>8.1</b></a></li>
    19221911                  <li class="indline1"><em>RFC2616</em>&nbsp;&nbsp;<a class="iref" href="#RFC2616"><b>8.2</b></a>, <a class="iref" href="#rfc.xref.RFC2616.1">C.1</a></li>
    … …  
    19431932            </li>
    19441933            <li class="indline0"><a id="rfc.index.W" href="#rfc.index.W"><b>W</b></a><ul class="ind">
    1945                   <li class="indline1">Warning header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.7</a>, <a class="iref" href="#rfc.iref.w.1"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.1</a>, <a class="iref" href="#rfc.xref.header.warning.4">A.1</a></li>
     1934                  <li class="indline1">Warning header&nbsp;&nbsp;<a class="iref" href="#rfc.xref.header.warning.1">2.3.3</a>, <a class="iref" href="#rfc.xref.header.warning.2">2.7</a>, <a class="iref" href="#rfc.iref.w.1"><b>3.6</b></a>, <a class="iref" href="#rfc.xref.header.warning.3">5.1</a>, <a class="iref" href="#rfc.xref.header.warning.4">A.1</a>, <a class="iref" href="#rfc.xref.header.warning.5">A.2</a></li>
    19461935               </ul>
    19471936            </li>

  • draft-ietf-httpbis/latest/p6-cache.xml

    r662 r669  
    14201420<t>
    14211421  Multiple warnings can be attached to a response (either by the origin server or by
    1422   a cache), including multiple warnings with the same code number. For example, a server
    1423   might provide the same warning with texts in both English and Basque.
     1422  a cache), including multiple warnings with the same code number, only differing
     1423  in warn-text.
    14241424</t>
    14251425<t>
    14261426  When this occurs, the user agent &SHOULD; inform the user of as many of them as
    1427   possible, in the order that they appear in the response. If it is not possible to inform
    1428   the user of all of the warnings, the user agent &SHOULD; follow these heuristics:
    1429   <list style="symbols">
    1430     <t>Warnings that appear early in the response take priority over those appearing later
    1431       in the response.</t>
    1432     <t>Warnings in the user's preferred character set take priority over warnings in other
    1433       character sets but with identical warn-codes and warn-agents.</t>
    1434   </list>
     1427  possible, in the order that they appear in the response.
    14351428</t>
    14361429<t>
    … …  
    14511444      returned, in which case they &MUST; be.</t>
    14521445  </list>
    1453 </t>
    1454 <t>
    1455   The warn-text &SHOULD; be in a natural language and character set that is most likely
    1456   to be intelligible to the human user receiving the response. This decision can be based on
    1457   any available knowledge, such as the location of the cache or user, the Accept-Language
    1458   field in a request, the Content-Language field in a response, etc. The default language is
    1459   English and the default character set is ISO-8859-1 (<xref target="ISO-8859-1" />).
    1460 </t>
    1461 <t>
    1462   If a character set other than ISO-8859-1 is used, it &MUST; be encoded in the
    1463   warn-text using the method described in <xref target="RFC2047" />.
    14641446</t>
    14651447<t>
    … …  
    16621644<references title="Normative References">
    16631645
    1664   <reference anchor="ISO-8859-1">
    1665     <front>
    1666       <title> Information technology -- 8-bit single-byte coded graphic character sets -- Part
    1667         1: Latin alphabet No. 1 </title>
    1668       <author>
    1669         <organization>International Organization for Standardization</organization>
    1670       </author>
    1671       <date year="1998" />
    1672     </front>
    1673     <seriesInfo name="ISO/IEC" value="8859-1:1998" />
    1674   </reference>
    1675 
    16761646  <reference anchor="Part1">
    16771647    <front>
    … …  
    19421912    <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;" />
    19431913    <x:source basename="p7-auth" href="p7-auth.xml" />
    1944   </reference>
    1945 
    1946   <reference anchor="RFC2047">
    1947     <front>
    1948       <title abbrev="Message Header Extensions">MIME (Multipurpose Internet Mail Extensions)
    1949         Part Three: Message Header Extensions for Non-ASCII Text</title>
    1950       <author fullname="Keith Moore" initials="K." surname="Moore">
    1951         <organization>University of Tennessee</organization>
    1952         <address><email>moore@cs.utk.edu</email></address>
    1953       </author>
    1954       <date month="November" year="1996" />
    1955     </front>
    1956     <seriesInfo name="RFC" value="2047" />
    19571914  </reference>
    19581915
    … …  
    21192076  Clarify denial of service attack avoidance requirement.
    21202077  (<xref target="invalidation.after.updates.or.deletions" />)
     2078</t>
     2079<t>
     2080  Do not mention RFC 2047 encoding and multiple languages in Warning headers
     2081  anymore, as these aspects never were implemented.
     2082  (<xref target="header.warning" />)
    21212083</t>
    21222084</section>
    … …  
    23462308<section anchor="changes.since.07" title="Since draft-ietf-httpbis-p6-cache-07">
    23472309<t>
    2348   None.
     2310  Closed issues:
     2311  <list style="symbols">
     2312    <t>
     2313      <eref target="http://tools.ietf.org/wg/httpbis/trac/ticket/187"/>:
     2314      "RFC2047 and warn-text"
     2315    </t>
     2316  </list>
    23492317</t>
    23502318</section>
Note: See TracChangeset for help on using the changeset viewer.