Compression iRules - GZIP vs. Deflate Preference

Ok, this workaround seems to work and my CONTENT-ENCODING Headers are now properly showing as GZIP. Getting this fixed soon would be great and since you guys usually GUI-ify any rule that gets alot of use, you should probably add this GZIP vs. DEFALTE Rule to the HTTP Profile in 9.0.

 

 

 

Some questions then:

 

===========================================================

 

1.) Is the perf hit on this workaround rule significantly more than the original one?

 

 

2.) Based on the way I am interpreting the workaround rule it appears that the top part is the same as the original rule we tried and the bottom part tells BIGIP to re-write the ACCEPT-ENCODING Header request from the Client so that BIGIP never sees the Deflate Option in the Client's request. If this is the case, why do we still need the original rule as part of this workaround rule?

 

 

3.) How would the workaround rule handle a situation where my browser supports Compression but only the Deflate method and not GZIP. If I am reading the rule correctly if BIGIP got an ACCEPT-ENCODING Header with just Deflate in it, BIGIP would parse it, see that the ACCEPT-ENCODING Header is present and then just re-write it to GZIP which the Client wouldn't support in this case. Granted I am not sure if there is a Browser version that support only Deflate but I thought I'd ask.

 

 

-t