Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I found that Goggle Chrome supports ssl compression and Firefox should support it soon.

I'm trying to configure Apache to to disable http compression if the ssl compression is used to prevent CPU overhead with the configuration option:


While the custom log (using %{SSL_COMPRESS_METHOD}x) shows that the ssl layer compression method is DEFLATE, the above option did not work and the http response content is still being compressed by Apache.

I had to use the option:

BrowserMatchNoCase ".*Chrome.*" no-gzip

I prefer if there is more general method in case other browsers support ssl compression in future or someone has a version of Chrome that does not have ssl compression.

share|improve this question
up vote 3 down vote accepted

Now after I got more information about the problem, I should answer my own question. This is a reported bug in Apache; Bug 49057 - setenvif should have access to SSL environment variables.

The bug is fixed in Apache 2.4.1 but this is not an option as I'm using CentOS 6.x.

I'll see if I can set no-gzip environment variable through the application instead of the Apache config.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.