- From: Larry Masinter <masinter@parc.xerox.com>
- Date: Wed, 3 Jul 1996 15:38:46 PDT
- To: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com
This fixes Roy's nits and another couple that turned up when I read this out loud to Jim. ================================================================ # Some HTTP/1.0 servers have sent a Content-Type header without a # charset parameter to mean "recipient should guess". This is # inappropriate behavior, and HTTP/1.1 servers MUST NOT omit the # charset parameter of text media unless the charset of the data is # ISO-8859-1 (or the US-ASCII subset). # # Unfortunately, some older HTTP/1.0 clients did not deal properly # with an explicit charset parameter. Senders MAY include a charset # parameter even when the charset is ISO-8859-1 and SHOULD do so when # it is known that it will not confuse the recipient. HTTP/1.1 # recipients MUST respect the charset label provided by the sender; # those user agents that have a provision to "guess" a charset MUST # use the charset from the content-type field if they support that # charset, rather than the recipient's preference, when initially # displaying a document.
Received on Wednesday, 3 July 1996 15:45:05 UTC