Re: Parameters in Content-Type: headers; what the???

"Jon P. Knight" <>
Date: Wed, 25 May 1994 10:22:03 +0200
Message-id: <Pine.3.05.9405250935.A543-b100000@suna>
Precedence: bulk
From: "Jon P. Knight" <>
To: Multiple recipients of list <>
Subject: Re: Parameters in Content-Type: headers; what the???
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas
Content-Type: TEXT/PLAIN; charset=US-ASCII
Content-Type: TEXT/PLAIN; charset=US-ASCII
Mime-Version: 1.0
Mime-Version: 1.0
On Tue, 24 May 1994, Marc VanHeyningen wrote:
> It appears as though either:
> - I am misreading the spec, and parameters specifying the character
>   set should not be used for text/plain objects
> - Most of the existing browsers are broken; servers don't generate
>   parameters, so browsers don't bother to handle them properly even
>   though they're in the spec
> So, which is it?  And what do we do about it?

I'd say myself that you are in the right and most of the browsers are
broken.  The only thing to do about it is to send in bug reports to the
various browser writers and then, after they've had some time to
assimilate the bug fix into a new release, start deploying servers that
follow the spec as well.  This is the only way forward that I can see if
HTTP is going to start using kosher MIME as I think it should.


Jon Knight, Research Student in High Performance Networking and Distributed
Systems in the Department of _Computer_Studies_ at Loughborough University.
* Its not how big your share is, its how much you share that's important. *