Which could be the cause if removing the Accept-Encoding header does not result in compression being performed by the Citrix ADC?

• A. Servercmp is disabled on the Citrix ADC.
• B. The Compression Policy needs to be reconfigured.
• C. The rewrite policy is bound at an incorrect bind point.
• D. The servers are automatically compressing all responses.

Answer: (D)

Compression in HTTP can happen either at the backend servers or at the Citrix ADC, depending on configuration. The Accept-Encoding header signals to a compressor that the client can handle compressed content, and the ADC will compress responses when a compression policy is active. If, after removing Accept-Encoding, you still see compressed responses, the likely cause is that the upstream servers are automatically compressing all responses. In that situation, the content is already compressed before it reaches the ADC, so the ADC won’t re-compress it, and removing the header doesn’t trigger ADC compression. To verify, check the response for Content-Encoding and review the backend server configurations to see if they’re set to always compress. If you want the ADC to handle compression, you’d need to adjust the upstream server behavior or ensure the ADC’s compression policy is in effect and that servers aren’t pre-compressing.