Hi,
GZip is just a wrapped set of headers around deflate.
Deflate includes a few small headers such as any initial data that will get better compression always, the compression rate (none/normal/best), etc. Deflate also includes an Adler32 checksum at the end.
GZip adds some additional headers to the start (algorithm always deflate anyway), file name etc and a CRC32 checksum to the end.This means that deflate will always be slightly faster (less to initialise, no CRC32 checksum) and save you a few bytes (no GZip headers) just the deflate headers that are inside the GZip headers for GZip compression anyway).
Now you need to see what is client coming with in "ACCEPT-ENCODING". If client comes with both GZIP/DEFLATE then ACE uses the configured method. Example below from TS guide.
policy-map type loadbalance first-match L7_COMP_SLB_POLICY
class L7default-compression-exclusion-mime-type_CLASS
serverfarm SFARM1
class class-default
serverfarm SFARM1
compress default-method deflate policy-map type loadbalance first-match L7_COMP_SLB_POLICY
class L7default-compression-exclusion-mime-type_CLASS
serverfarm SFARM1
class class-default
serverfarm SFARM1
compress default-method deflate --------------->Configured method
Both methods are supported and good and generally "Deflate" is considered to be better because of less overhead and as a result less bytes. I don't have examples when to use which.
Regards,
Kanwal
