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

On Mon, 2005-08-08 at 05:56 -0500, William A. Rowe, Jr. wrote:
..
> >RFC2616 normatively refers to RFC2396 for the definitions of URI components (<http://greenbytes.de/tech/webdav/rfc2616.html#rfc.section.3.2.1>). And RFC2396 did not allow non-ASCII characters in URIs, either.
> 
> Julian stop it already; we -know- that only non-reserved, 
> ASCII characters can be transmitted over the wire.  The
> question Robert raises is what charset is normative prior
> to it being encoded for transmission over the wire.  2396
> says nothing that the %-escape decoded value must be be ASCII
> for all components, quoting RFC 2396 section 2;
> 
>   "
...
> ahhh... "or by an escape encoding" - which is all Robert has asked
> for since the conversation started ;-)  Yet - we still don't have
> a definitive charset, it's opaque octet data.

Yes!

> >>That said; for example WinNT's filesystem is truly unicode, which Apache
> >>2.0, for example, treats as a utf-8 filesystem for resource names.  The
> >>typical *nix system today may in fact use utf-8 file names, but does
> >>not enforce them (they remain opaque octets to the posix layer).  It's
> >>entirely up to the implementor what to serve based on a URI.
> >
> >Yes. That's a problem. See <http://greenbytes.de/tech/webdav/draft-reschke-webdav-url-constraints-latest.html> for a work-in-progress attempt to fix things at least for WebDAV.
> 
> Ack :)  The more comprehensive solution of course, HTTP/1.2, 
> although I know some have their hearts set on HTTP-NG first.

I'd be happy with a HTTP/1.1 errata that updates the http:// scheme to
declare it as utf8 before the escape encoding is done.

Cheers,
Rob

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