Iron (Chrome/Chromium) has problems with Sidki filters

[sidki3003]

Re issue with release config: what JJoe says.

The difference between release config:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US)
...and alpha config:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US) AppleWebKit/533.99
...is that i came across a couple of sites lately, testing for "AppleWebKit". Writing back this string also enables the multi-post iframe in DSLR replies.

Now, DSLR's compression check is testing for "gecko", which happens to be present in: (KHTML, like Gecko)

So, for the alpha i prefer a generic approach, i.e. replacing the existing Mozilla block in User-Agents.ptxt with:

Code:

## If Firefox, SeaMonkey, Chrome, Safari:
## ----------------------------------------------------------------------------
Mozilla/5.0(^$TST(keyword=*.f_ua_(^[a-z]++moz)*))(*(; rv:*Gecko/[#*:*]
  ( Firefox/[#*:*].[#*:*]$SET(3=.9.9)|)|\)
  (*\s(Gecko/[#*:*]|AppleWebKit/(*.)+{1}$SET(3=99))|))\2
  [0-9.]+( $NEST(\(,*gecko*,\))|)\4|$SET(2=\)))
  $SET(1=Mozilla/5.0 \(Windows; U; Windows NT 6.1; en-US\2\3\4)

Let me know if you suspect these conclusions being incorrect.


Graycode: Very interesting observation!
The configs aren't affected, however. In the outbound accept-encoding header everything but gzip & deflate is discarded.

edit (Sep 10): list expression updated