[
Lists Home |
Date Index |
Thread Index
]
Just a small note.
On Wed, 14 Jan 2004 18:13:26 -0800
Joe English <jenglish@flightlab.com> wrote:
[* supplied to indicate absence of the charset parameter from the
Content-type header ]
> [*] Which means either "US-ASCII" or "ISO-8859-1", depending
> on which RFC you take as authoritative.
Actually, you haven't a choice. RFC 2616 is authoritative for HTTP,
which is not a MIME-compliant protocol. It just abuses the
MIME-reserved prefix "Content-" and reuses some MIME-defined headers to
carry more-or-less the same information, only with different defaults.
Lack of a charset parameter in the Content-Type header of HTTP always
means ISO-8859-1, and never means US-ASCII. Lack of a charset parameter
(or of a Content-Type header altogether) in a MIME-compliant protocol
always means US-ASCII. But HTTP also fails to include a MIME-Version
header (required for MIME compliance) and specifically forbids
Content-Transfer-Encoding. MIME-compliant protocols may leave
Content-Transfer-Encoding out, but absence implies "7bit". In HTTP,
required absence means "binary", and because it must not be present, you
cannot send 7bit or 8bit via HTTP, thank you very much (not that you
need to, anyway).
Amy!
(being a MIME pedant, alas)
--
Amelia A. Lewis amyzing {at} talsever.com
I don't know that I ever wanted greatness, on its own. It seems rather
like wanting to be an engineer, rather than wanting to design something,
or wanting to be a writer, rather than wanting to write. It should be a
by-product, not a thing in itself. Otherwise, it's just an ego trip.
-- Merlin, son of Corwin, Prince of Chaos (Roger Zelazny)
|
