Re: http charset labelling

Larry Masinter (masinter@parc.xerox.com)
Wed, 31 Jan 1996 18:43:40 PST


To: keld@dkuug.dk
Cc: uri@bunyip.com
In-Reply-To: Keld J|rn Simonsen's message of Wed, 31 Jan 1996 08:55:50 -0800 <199601311655.RAA19593@dkuug.dk>
Subject: Re: http charset labelling
From: Larry Masinter <masinter@parc.xerox.com>
Message-Id: <96Jan31.184342pst.2733@golden.parc.xerox.com>
Date: Wed, 31 Jan 1996 18:43:40 PST

It would not require changing any existing specification for someone
to create a web server that interpreted

   http://host.dom/encoding/selector

to mean that 'encoding' was a particular encoding of the given
selector. The web server could even return a 'Location:' header in the
results that would give a canonical encoding, just so as not to
confuse caches.

'encoding' could even be UTF7, for example.