W3C home > Mailing lists > Public > ietf-http-wg-old@w3.org > May to August 1996

Re: re-revised last last words

From: <jg@w3.org>
Date: Wed, 03 Jul 96 20:19:43 -0400
Message-Id: <9607040019.AA20861@zorch.w3.org>
To: Larry Masinter <masinter@parc.xerox.com>
Cc: http-wg%cuckoo.hpl.hp.com@hplb.hpl.hp.com, jg@w3.org
X-Mailing-List: <http-wg@cuckoo.hpl.hp.com> archive/latest/1028

There was a redundant sentence (with the last sentence of the
preceeding paragraph) in Larry's last version, and I did a bit
of reorganization.  This is what I ended up with:

Some HTTP/1.0 software has interpreted a Content-Type header without
charset parameter incorrectly to mean "recipient should guess."
Senders wishing to defeat this behavior 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.

Unfortunately, some older HTTP/1.0 clients did not deal properly with
an explicit charset parameter. HTTP/1.1 recipients MUST respect the
charset label provided by the sender; and 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 17:25:08 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 14:40:17 UTC