Changeset 121 for draft-ietf-httpbis/latest/p3-payload.html
- Timestamp:
- 31/12/07 17:08:48 (14 years ago)
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
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>
Note: See TracChangeset
for help on using the changeset viewer.