Iron (Chrome/Chromium) has problems with Sidki filters

[Graycode]

Here's an interesting blog about the upcoming IE9's use of a short User-Agent string:
http://zoompf.com/blog/2010/03/the-big-p...king-about

I always thought it odd that a server would look at both the Accept-Encoding and the User-Agent headers to determine whether to reply with compression.

Quote:Unfortunately there are some bugs in certain older web browsers where these browsers would send an Accept-Encoding header telling the web server they supported HTTP compression when they really didn’t. The biggest culprit was IE6 before SP1. This browser had a bug would it would internally cache the compressed version of a CSS or JavaScript response and would try (and fail) to directly process the compress bytes. There are also certain versions of Netscape 4.x that did not properly handle HTTP compression despite using Accept-Encoding to instruct the server that it did.

Too bad some servers look for User-Agent strings they know to be good vs. only using exceptions to identify those that are faulty.

It's nice that Microsoft won't be disclosing as much crap in their UA any longer. Personally though I still don't think a web server needs to know my real computer architecture or the OS that browser's running in.