Re: URIEquivalence-15: characters in RFC 2396 (was: Re: [Minutes] 27 Jan 2003 TAG teleconf (..., IRIEverywhere-27, ...))


without bothering the least with my shallow understanding of things:

Am Dienstag, 04.02.03, um 23:52 Uhr (Europe/Berlin) schrieb Martin 

>> To come back to the one character or three question... '%7e' might be 
>> viewed
>> as 3 "URI Characters"; one "octet"; and one "original character" '~'
>> (maybe).
> Yes, exactly. The 'maybe' for '~' is quite appropriate.
> If somebody ran an http server on a computer where people
> still used e.g. the German version of ISO 646
> (see, then
> the original character would be a sharp-s.

But if the "%7e" is part of the query, then:

says that it is encoded US-ASCII.

So, http URIs can be encoded from an arbitrary charset, apart from
the query part?

While HTML4 is not normative for RFC 2396, it certainly reflects a way 
thinking about http uri encoding which is quite, uh, widespread nowadays
(in heads and implementations).

If this way of thinking is broken, then I would be interested to know
how a HTTP Server/CGI Util Package/Servlet Container is supposed to
translate a GET on

IMHO, "undefined" is not an acceptable answer.



Received on Wednesday, 5 February 2003 10:28:43 UTC