Re: Proposal on removing Content Negotiation from http 1.1

> Netscape Navigator does look for "charset", but if it's omitted, we
> default to whatever the user has set in the "encoding" menu. We don't
> like having to present these confusing choices to the user, but the
> current Web infrastructure doesn't use "charset" at all (or very
> little).

Because Web just started to move beyond iso-8859-1 universe. :-)

Received on Wednesday, 24 January 1996 14:33:17 UTC