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

The official documentation for mod_deflate works, and gives me nice results so far on my serveR. Are there any changes anyone suggests for use on a production machine?

<Location />
# Insert filter
SetOutputFilter DEFLATE

# Netscape 4.x has some problems...
BrowserMatch ^Mozilla/4 gzip-only-text/html

# Netscape 4.06-4.08 have some more problems
BrowserMatch ^Mozilla/4\.0[678] no-gzip

# MSIE masquerades as Netscape, but it is fine
BrowserMatch \bMSIE !no-gzip !gzip-only-text/html
# Don't compress images
SetEnvIfNoCase Request_URI \
\.(?:gif|jpe?g|png)$ no-gzip dont-vary

# Make sure proxies don't deliver the wrong content
Header append Vary User-Agent env=!dont-vary
share|improve this question
It certainly won't hurt to use that in a production setup, but it looks pretty conservative, and is probably based on reality as it stood several years ago. I'm hoping the super-geniuses here will post an "optimal" mod_deflate configuration for today's world. – Jed Daniels Jun 24 '10 at 16:59
up vote 2 down vote accepted

The tradeoff you have to make is time versus size. If you spend time changing the compression level, it might take a few milliseconds more to serve the page for a minimal benefit in making the compressed page smaller.

The defaults are fairly well balanced, handle 99% of the browsers correctly and are well thought out.

share|improve this answer
sounds like a plan to use the defaults then! I've gotten great compression so far – solsol Jun 25 '10 at 14:02

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.