W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2005

Re: location uri, ucs and the http scheme definition.

From: Robert Collins <robertc@robertcollins.net>
Date: Mon, 08 Aug 2005 03:21:29 +0000
To: Julian Reschke <julian.reschke@gmx.de>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <1123471303.12992.13.camel@localhost.localdomain>
On Thu, 2005-08-04 at 12:19 +0200, Julian Reschke wrote:
> Robert Collins wrote:
> > So: what is the correct encoding approach for non US-ASCII characters in
> > HTTP URI's in Location: ?
> 
> What does this have to do with "Location"? A URI never ever contains 
> non-ASCII characters, no matter where it appears.

Uhm. URIs do contain non-ASCII characters quite commonly. Such as
http://example.com/~usÚrname

Note that that cannot be unambiguously percent escaped from the rules
contained in rfc2616 and std66. The missing link is the encoding to use
before percent escaping, which you suggest a heuristic ..

> That being said; the *best* way (if you control the server) to embed non 
> ASCII data into a URI usually is to UTF-8 encode, then percent-escape.

What I'm asking for is current RFC or std document that specifies this.
The reference for Location is because Location is the header I currently
need to ensure correct encoding of, and its definition is 'absoluteURI'
in rfc2616, which is incorporated from ... and thus we trace through to
std66 which passes the buck for the canonical pre-percent-escape
encoding back to the standard defining the URI scheme, which is rfc2616.
Full circle and no stance taken.

Rob

-- 
GPG key available at: <http://www.robertcollins.net/keys.txt>.

Received on Monday, 8 August 2005 07:07:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:49:40 GMT