Changeset 121
- Timestamp:
- 31/12/07 17:08:48 (15 years ago)
- Location:
- draft-ietf-httpbis/latest
- Files:
-
- 6 edited
Legend:
- Unmodified
- Added
- Removed
-
draft-ietf-httpbis/latest/p1-messaging.html
r120 r121 939 939 <div id="rfc.figure.u.6"></div><pre class="inline"><span id="rfc.iref.g.14"></span> LWS = [CRLF] 1*( SP | HT ) 940 940 </pre><p id="rfc.section.2.2.p.7">The TEXT rule is only used for descriptive field contents and values that are not intended to be interpreted by the message 941 parser. Words of *TEXT <em class="bcp14">MAY</em> contain characters from character sets other than ISO-8859-1 <a href="#ISO-8859 " id="rfc.xref.ISO-8859.1"><cite title="Information technology - 8-bit single byte coded graphic - character sets">[ISO-8859]</cite></a> only when encoded according to the rules of <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>.941 parser. Words of *TEXT <em class="bcp14">MAY</em> contain characters from character sets other than 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> only when encoded according to the rules of <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>. 942 942 </p> 943 943 <div id="rfc.figure.u.7"></div><pre class="inline"><span id="rfc.iref.g.15"></span> TEXT = <any OCTET except CTLs, … … 1943 1943 <h2 id="rfc.references.1"><a href="#rfc.section.12.1" id="rfc.section.12.1">12.1</a> Normative References 1944 1944 </h2> 1945 <table summary="Normative References"> 1945 <table summary="Normative References"> 1946 <tr> 1947 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 1948 <td class="top">International Organization for Standardization, “ 1949 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1950 ”, ISO/IEC 8859-1:1998, 1998. 1951 </td> 1952 </tr> 1946 1953 <tr> 1947 1954 <td class="reference"><b id="Part2">[Part2]</b></td> … … 1981 1988 <h2 id="rfc.references.3"><a href="#rfc.section.12.3" id="rfc.section.12.3">12.3</a> References (to be categorized) 1982 1989 </h2> 1983 <table summary="References (to be categorized)"> 1984 <tr> 1985 <td class="reference"><b id="ISO-8859">[ISO-8859]</b></td> 1986 <td class="top">International Organization for Standardization, “Information technology - 8-bit single byte coded graphic - character sets”, 1987-1990.<br>Part 1: Latin alphabet No. 1, ISO-8859-1:1987. Part 2: Latin alphabet No. 2, ISO-8859-2, 1987. Part 3: Latin alphabet No. 1987 3, ISO-8859-3, 1988. Part 4: Latin alphabet No. 4, ISO-8859-4, 1988. Part 5: Latin/Cyrillic alphabet, ISO-8859-5, 1988. Part 1988 6: Latin/Arabic alphabet, ISO-8859-6, 1987. Part 7: Latin/Greek alphabet, ISO-8859-7, 1987. Part 8: Latin/Hebrew alphabet, 1989 ISO-8859-8, 1988. Part 9: Latin alphabet No. 5, ISO-8859-9, 1990. 1990 </td> 1991 </tr> 1990 <table summary="References (to be categorized)"> 1992 1991 <tr> 1993 1992 <td class="reference"><b id="Nie1997">[Nie1997]</b></td> … … 2516 2515 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 2517 2516 <li class="indline1">inbound <a class="iref" href="#rfc.iref.i.1">1.3</a></li> 2518 <li class="indline1"><em>ISO-8859 </em> <a class="iref" href="#rfc.xref.ISO-8859.1">2.2</a>, <a class="iref" href="#ISO-8859"><b>12.3</b></a></li>2517 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.2</a>, <a class="iref" href="#ISO-8859-1"><b>12.1</b></a></li> 2519 2518 </ul> 2520 2519 </li> -
draft-ietf-httpbis/latest/p1-messaging.xml
r120 r121 855 855 that are not intended to be interpreted by the message parser. Words 856 856 of *TEXT &MAY; contain characters from character sets other than ISO-8859-1 857 <xref target="ISO-8859 "/> only when encoded according to the rules of857 <xref target="ISO-8859-1"/> only when encoded according to the rules of 858 858 <xref target="RFC2047"/>. 859 859 </t> … … 2912 2912 2913 2913 <references title="Normative References"> 2914 2915 <reference anchor="ISO-8859-1"> 2916 <front> 2917 <title> 2918 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 2919 </title> 2920 <author> 2921 <organization>International Organization for Standardization</organization> 2922 </author> 2923 <date year="1998"/> 2924 </front> 2925 <seriesInfo name="ISO/IEC" value="8859-1:1998"/> 2926 </reference> 2914 2927 2915 2928 <reference anchor="Part2"> … … 3474 3487 </reference> 3475 3488 3476 <reference anchor="ISO-8859">3477 <front>3478 <title>Information technology - 8-bit single byte coded graphic - character sets</title>3479 <author>3480 <organization>International Organization for Standardization</organization>3481 </author>3482 <date year="1987-1990"/>3483 </front>3484 <annotation>3485 Part 1: Latin alphabet No. 1, ISO-8859-1:1987.3486 Part 2: Latin alphabet No. 2, ISO-8859-2, 1987.3487 Part 3: Latin alphabet No. 3, ISO-8859-3, 1988.3488 Part 4: Latin alphabet No. 4, ISO-8859-4, 1988.3489 Part 5: Latin/Cyrillic alphabet, ISO-8859-5, 1988.3490 Part 6: Latin/Arabic alphabet, ISO-8859-6, 1987.3491 Part 7: Latin/Greek alphabet, ISO-8859-7, 1987.3492 Part 8: Latin/Hebrew alphabet, ISO-8859-8, 1988.3493 Part 9: Latin alphabet No. 5, ISO-8859-9, 1990.3494 </annotation>3495 </reference>3496 3497 3489 <reference anchor="RFC1900"> 3498 3490 <front> -
draft-ietf-httpbis/latest/p3-payload.html
r120 r121 607 607 <h3 id="rfc.section.2.1.1"><a href="#rfc.section.2.1.1">2.1.1</a> <a id="missing.charset" href="#missing.charset">Missing Charset</a></h3> 608 608 <p id="rfc.section.2.1.1.p.1">Some HTTP/1.0 software has interpreted a Content-Type header without charset parameter incorrectly to mean "recipient should 609 guess." Senders wishing to defeat this behavior <em class="bcp14">MAY</em> include a charset parameter even when the charset is ISO-8859-1 and <em class="bcp14">SHOULD</em> do so when it is known that it will not confuse the recipient.609 guess." Senders wishing to defeat this behavior <em class="bcp14">MAY</em> include a charset parameter even when the charset 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>) and <em class="bcp14">SHOULD</em> do so when it is known that it will not confuse the recipient. 610 610 </p> 611 611 <p id="rfc.section.2.1.1.p.2">Unfortunately, some older HTTP/1.0 clients did not deal properly with an explicit charset parameter. HTTP/1.1 recipients <em class="bcp14">MUST</em> respect the charset label provided by the sender; and those user agents that have a provision to "guess" a charset <em class="bcp14">MUST</em> use the charset from the content-type field if they support that charset, rather than the recipient's preference, when initially … … 1204 1204 <h2 id="rfc.references.1"><a href="#rfc.section.9.1" id="rfc.section.9.1">9.1</a> Normative References 1205 1205 </h2> 1206 <table summary="Normative References"> 1206 <table summary="Normative References"> 1207 <tr> 1208 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 1209 <td class="top">International Organization for Standardization, “ 1210 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1211 ”, ISO/IEC 8859-1:1998, 1998. 1212 </td> 1213 </tr> 1207 1214 <tr> 1208 1215 <td class="reference"><b id="Part1">[Part1]</b></td> … … 1615 1622 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 1616 1623 <li class="indline1">identity <a class="iref" href="#rfc.iref.i.1">2.2</a></li> 1624 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">2.1.1</a>, <a class="iref" href="#ISO-8859-1"><b>9.1</b></a></li> 1617 1625 </ul> 1618 1626 </li> -
draft-ietf-httpbis/latest/p3-payload.xml
r120 r121 292 292 charset parameter incorrectly to mean "recipient should guess." 293 293 Senders wishing to defeat this behavior &MAY; include a charset 294 parameter even when the charset is ISO-8859-1 and &SHOULD; do so when294 parameter even when the charset is ISO-8859-1 (<xref target="ISO-8859-1"/>) and &SHOULD; do so when 295 295 it is known that it will not confuse the recipient. 296 296 </t> … … 1453 1453 1454 1454 <references title="Normative References"> 1455 1456 <reference anchor="ISO-8859-1"> 1457 <front> 1458 <title> 1459 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1460 </title> 1461 <author> 1462 <organization>International Organization for Standardization</organization> 1463 </author> 1464 <date year="1998"/> 1465 </front> 1466 <seriesInfo name="ISO/IEC" value="8859-1:1998"/> 1467 </reference> 1455 1468 1456 1469 <reference anchor="Part1"> -
draft-ietf-httpbis/latest/p6-cache.html
r120 r121 1649 1649 <p id="rfc.section.3.6.p.5">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. 1650 1650 This decision <em class="bcp14">MAY</em> be based on any available knowledge, such as the location of the cache or user, the Accept-Language field in a request, the 1651 Content-Language field in a response, etc. The default language is English and the default character set is ISO-8859-1 .1651 Content-Language field in a response, etc. The default language is English and the default character set 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>). 1652 1652 </p> 1653 1653 <p id="rfc.section.3.6.p.6">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>. … … 1734 1734 <h2 id="rfc.references.1"><a href="#rfc.section.7.1" id="rfc.section.7.1">7.1</a> Normative References 1735 1735 </h2> 1736 <table summary="Normative References"> 1736 <table summary="Normative References"> 1737 <tr> 1738 <td class="reference"><b id="ISO-8859-1">[ISO-8859-1]</b></td> 1739 <td class="top">International Organization for Standardization, “ 1740 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 1741 ”, ISO/IEC 8859-1:1998, 1998. 1742 </td> 1743 </tr> 1737 1744 <tr> 1738 1745 <td class="reference"><b id="Part1">[Part1]</b></td> … … 1874 1881 <p>Funding for the RFC Editor function is provided by the IETF Administrative Support Activity (IASA).</p> 1875 1882 <h1 id="rfc.index"><a href="#rfc.index">Index</a></h1> 1876 <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>1883 <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> 1877 1884 </p> 1878 1885 <div class="print2col"> … … 1954 1961 </li> 1955 1962 <li class="indline1">heuristic expiration time <a class="iref" href="#rfc.iref.h.1">1.2</a></li> 1963 </ul> 1964 </li> 1965 <li class="indline0"><a id="rfc.index.I" href="#rfc.index.I"><b>I</b></a><ul class="ind"> 1966 <li class="indline1"><em>ISO-8859-1</em> <a class="iref" href="#rfc.xref.ISO-8859-1.1">3.6</a>, <a class="iref" href="#ISO-8859-1"><b>7.1</b></a></li> 1956 1967 </ul> 1957 1968 </li> -
draft-ietf-httpbis/latest/p6-cache.xml
r120 r121 2302 2302 as the location of the cache or user, the Accept-Language field in a 2303 2303 request, the Content-Language field in a response, etc. The default 2304 language is English and the default character set is ISO-8859-1 .2304 language is English and the default character set is ISO-8859-1 (<xref target="ISO-8859-1"/>). 2305 2305 </t> 2306 2306 <t> … … 2450 2450 2451 2451 <references title="Normative References"> 2452 2453 <reference anchor="ISO-8859-1"> 2454 <front> 2455 <title> 2456 Information technology -- 8-bit single-byte coded graphic character sets -- Part 1: Latin alphabet No. 1 2457 </title> 2458 <author> 2459 <organization>International Organization for Standardization</organization> 2460 </author> 2461 <date year="1998"/> 2462 </front> 2463 <seriesInfo name="ISO/IEC" value="8859-1:1998"/> 2464 </reference> 2452 2465 2453 2466 <reference anchor="Part1">
Note: See TracChangeset
for help on using the changeset viewer.