If you try to view a URL like "http://foo/bar\image.gif" in IE 6, the
browser will (incorrectly) send out a request-URI like
"/bar/image.gif" where Firefox 2 will (correctly) send out a
request-URI like "/bar%5Cimage.gif".

The funny part about it is that the servers treat it differently too.

If IIS gets a request-URI with a %5C in it, it'll translate that to "/".
If Apache 2 gets a request-URI like that, it's treated literally so it'll 404.

So if you're using the Microsoft product on either end, it saves you
from shooting yourself in the foot. The only combo that breaks in the
test cases of IIS, Apache, Firefox 2, and IE 6 is Firefox 2 -> Apache.
romanblack.com ID's itself as "apache"
Maybe that explains why half the time when I hear someone on the
television or radio read aloud a URL they say "backslash" when they
mean to say "slash". :)

imho doing whatever friendly thing you can to silently correct common
mistakes in cases like this is a good thing as long as it doesn't
interfere with too many other uses. It's how most people want products
to behave.
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist