Forum Discussion
AltostratusHTTP Compression fails for cached objects
It appears that the LTM (11.3.0) fails to compress cached objects. Anyone else run into this?
Even more strangely, after I had specifically excluded the CSS-file I was looking at from being cached (and it was now indeed getting compressed) I removed the cache exclusion. To my surprise the file is now getting compressed - even though it's also being cached.
The question is why this item first didn't get compressed (very consistently - I checked in various browsers from different locations), but now suddenly it is.
One more quirk: throughout my testing when I used cURL the LTM did compress the item - even though it was also cached.
2 Replies
ArieMore information:
Caching may not be a factor, as I had earlier changed the "include" item from "text/" to "text/(html/css)" to see if I could force CSS-files to get compressed. However, I didn't remove that before I fiddled with the cache.
What_Lies_Bene1Cirrostratus
The cache should hold compressed and uncompressed objects assuming both have previously been served. It doesn't compress objects itself. It'll serve one or the other based on what the client supports. Other than that, there is no relationship between the two features.
