Forum Discussion
G__Wesley_Rober
Jun 10, 2008Historic F5 Account
The http profile has all the appropriate settings to appropriately match URIs and content types. The real problem as I see it is that when you want to do "intelligent compression" beyond what is available in the http profile, you must use the "selective" setting in the profile. Unfortunately this setting does not do ANY compression by default. You must use the COMPRESS::enable command, which rightly ignores the content compression settings of the http profile, and will attempt to compress regardless of content type. My suggestion would be:
1) Allow the Compress: disable command when compression is enabled in the http profile.
or
2) Have the default behavior for selective compression actually compress according to the http profile settings.
It would make things a whole lot simpler. ;-)
Recent Discussions
Related Content
- May 24, 2019Former Member