I wasn't clear in my explanation, because I didn't quite
understand the issue.
If the server specifies the URL already encoded using the '%'
style encoding, then the URL arrives unmodified:
http://localhost/bj%F6rn
On the other hand if I specify the URL with a character name
(is this accepted in the specs?), e.g.:
http://localhost/é
Then the URL will be encoded differently according to whether the
page is ISO-8859-1 or UTF-8 (would this be represensitive of a URL
typed into the address bar as well?):
ISO-8859-1: http://localhost/%E9
utf-8: http://localhost/%C3%A9
Since the request header does not explicitly specify the page encoding,
unless I missed this, this makes it it difficult to know how to handle
the URL decoding.
Andr�
On Monday, Dec 23, 2002, at 08:59 America/Montreal, Ian Hickson wrote:
On Mon, 23 Dec 2002, Bjoern Hoehrmann wrote:
That's news to me. My Mozilla does the following. Typing the URI
http://localhost:99/björn into the address bar the browser requests
GET /bj%F6rn HTTP/1.1
That's ISO-8859-1 or a compatible encoding.
Oh, my bad. I assumed we were talking about form submissions. It is
possible I am mistaken even for those cases, though.
For links, if they are invalid (i.e. not correctly escaped), I believe
Mozilla will use the document encoding to form the URIs.
As I said, though, there is no spec (to my knowledge) that defines
this.
--
Ian Hickson )\._.,--....,'``.
fL
"meow" /, _.. \ _\ ;`._
,.
http://index.hixie.ch/
`._.-(,_..'--(,_..'`-.;.'
--
mailto:[EMAIL PROTECTED]
