Changeset 669 for draft-ietf-httpbis/latest/p6-cache.xml
- Timestamp:
- 07/08/09 05:52:56 (13 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p6-cache.xml
r662 r669 1420 1420 <t> 1421 1421 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 server1423 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. 1424 1424 </t> 1425 1425 <t> 1426 1426 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. 1435 1428 </t> 1436 1429 <t> … … 1451 1444 returned, in which case they &MUST; be.</t> 1452 1445 </list> 1453 </t>1454 <t>1455 The warn-text &SHOULD; be in a natural language and character set that is most likely1456 to be intelligible to the human user receiving the response. This decision can be based on1457 any available knowledge, such as the location of the cache or user, the Accept-Language1458 field in a request, the Content-Language field in a response, etc. The default language is1459 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 the1463 warn-text using the method described in <xref target="RFC2047" />.1464 1446 </t> 1465 1447 <t> … … 1662 1644 <references title="Normative References"> 1663 1645 1664 <reference anchor="ISO-8859-1">1665 <front>1666 <title> Information technology -- 8-bit single-byte coded graphic character sets -- Part1667 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 1676 1646 <reference anchor="Part1"> 1677 1647 <front> … … 1942 1912 <seriesInfo name="Internet-Draft" value="draft-ietf-httpbis-p7-auth-&ID-VERSION;" /> 1943 1913 <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" />1957 1914 </reference> 1958 1915 … … 2119 2076 Clarify denial of service attack avoidance requirement. 2120 2077 (<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" />) 2121 2083 </t> 2122 2084 </section> … … 2346 2308 <section anchor="changes.since.07" title="Since draft-ietf-httpbis-p6-cache-07"> 2347 2309 <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> 2349 2317 </t> 2350 2318 </section>
Note: See TracChangeset
for help on using the changeset viewer.