how Windows browsers encode URL [Re: why the % cruft?]

[Toshitaka Fujioka]

On Wednesday 10 July 2002 01:37, Vadim Plessky wrote:
> On Tuesday 09 July 2002 11:15 am, Waldo Bastian wrote:
> |  On Tuesday 09 July 2002 12:01 am, Lars Knoll wrote:
> |  > > URLs are spec'ed as a sequence of octets (8-bit values) "Unicode
> |  > > URLs" basically don't exist. Despite that we try to handle them
> |  > > anyway and appearantly that doesn't always work. (E.g. we need to
> |  > > convert unicode to an 8 bit sequence before we can tranfer it to the
> |  > > website but the encoding to use for that is unspecified, so we can
> |  > > only guess.)
> |  >
> |  > As Dirk already pointed out, IE sends URLS in utf8 by default. I'm
> |  > pretty sure we could do the same without breaking a lot of web pages
> |  > (they'd be broken with IE aswell). Maybe there's an HTTP header field
> |  > we can set to indicate this?
> |
> |  My impression was that many non-latin1 (e.g. russian, japanese, korean,
> | etc.) websites use the "local locale" as encoding and not utf8. Maybe
> | Vadim can comment on that from the Russian point of view.

[snip]
  
> So, it seems it's rather safe to encode URL to UTF8, as it's common pratice
> and acepted not only by MS IE, but by Mozilla aswell.

Please change Change Browser Identification or User Agent.
e.g. Mozilla M18n on Windows NT 4.0 or Gecko/20000110 or compatible; MSIE 6.0

then you get a result same as Mozilla or IE 6.0.

-- 
Toshitaka Fujioka
http://www.kde.org                The K Desktop Environment Project
                                                    fujioka at kde.org
http://www.kde.gr.jp               Japan KDE User's Group
                                                    toshitaka at kde.gr.jp

-- A journey of a thousand miles must begin with a single step.  Lao-zi --