Re: http charset labelling

Larry Masinter <masinter@parc.xerox.com> Thu, 01 February 1996 03:29 UTC

Received: from ietf.nri.reston.va.us by IETF.CNRI.Reston.VA.US id aa27943; 31 Jan 96 22:29 EST
Received: from CNRI.Reston.VA.US by IETF.CNRI.Reston.VA.US id aa27939; 31 Jan 96 22:29 EST
Received: from services.Bunyip.COM by CNRI.Reston.VA.US id aa18380; 31 Jan 96 22:29 EST
Received: (from daemon@localhost) by services.bunyip.com (8.6.10/8.6.9) id VAA08093 for uri-out; Wed, 31 Jan 1996 21:43:56 -0500
Received: from mocha.bunyip.com (mocha.Bunyip.Com [192.197.208.1]) by services.bunyip.com (8.6.10/8.6.9) with SMTP id VAA08087 for <uri@services.bunyip.com>; Wed, 31 Jan 1996 21:43:53 -0500
Received: from alpha.Xerox.COM by mocha.bunyip.com with SMTP (5.65a/IDA-1.4.2b/CC-Guru-2b) id AA23273 (mail destined for uri@services.bunyip.com); Wed, 31 Jan 96 21:43:51 -0500
Received: from golden.parc.xerox.com ([13.1.100.139]) by alpha.xerox.com with SMTP id <14822(1)>; Wed, 31 Jan 1996 18:43:43 PST
Received: by golden.parc.xerox.com id <2733>; Wed, 31 Jan 1996 18:43:42 -0800
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
Sender: ietf-archive-request@IETF.CNRI.Reston.VA.US
From: Larry Masinter <masinter@parc.xerox.com>
Fake-Sender: masinter@parc.xerox.com
Message-Id: <96Jan31.184342pst.2733@golden.parc.xerox.com>
Date: Wed, 31 Jan 1996 18:43:40 PST
X-Orig-Sender: owner-uri@bunyip.com
Precedence: bulk

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.