Browser Workarounds for HTTP Compression

if you want to see the effects of doing or not compression, you may want to try fiddler. It's Free :)

 

 

cheers!

The browser workarounds mostly relate to old versions of IE and Netscape. It's an all or nothing feature. If you want to disable compression for a specific browser and content type you'll need to write an iRule. Considering the size of most css and js these days I'm not sure why you would want to. I've not had issues with Mozilla based browsers for years.

Did you ever find out why the LTM wasn't using compressing when the request is made from Firefox? I'm wondering if the problem I'm encountering is the same one. If requests for CSS-files (text/css) are made from Chrome and Firefox the LTM doesn't use compression. However, if I use cURL to request the same file the LTM *does* compress the response. However, HTML-files *do* get compressed by the LTM, regardless of the client. When I look at the stats it shows that only HTML, JavaScript, and XML gets compressed; all other types show "0". The include list in the HTTP Compression profile features: application/(xml|x-javascript) text/ LTM 11.3.0

No, i didn't made progess on this one, i will query the tech-support. Even with 11.5.1 curl with a User-Agent of 'Mozilla/5.0' still disable the compression for text/css or application/javascript files.