HTTP Compression and the Vary Header

Thanks hoolio, but isnt it the case that you cant remove something via an iRule that a HTTP profile inserts?

 

 

I was thinking about doing it the other way around, so disabling the profile Vary insert, and using the iRule to insert a vary header only if the content length is above a certain limit that i know we will compress at. I guess i could just manipulate your sample to achieve the same thing.

 

 

The question still stands though to the developers as to why we would do something that seems redundant. i.e. inserting a vary header when the profile is never going to compress it.