Does mod_deflate skip gzip compression for responses smaller than DeflateBufferSize?

Question

Apache HTTP Server's mod_deflate controls gzip output through directives such as DeflateCompressionLevel and DeflateBufferSize, with compression normally enabled per MIME type via AddOutputFilterByType. The configuration goal is to serve gzipped application/octet-stream downloads with a consistent Content-Encoding: gzip header, a type that standard examples tend to leave out of the filter list.

What is unclear is how the filter treats a response whose body is smaller than the DeflateBufferSize value, the directive that sets the fragment size handed to zlib. It is not obvious from the directive descriptions whether such small payloads are compressed at all, whether the Content-Encoding header can differ between small and large responses of the same type, or whether the behavior changed between the 2.4 series and later releases. That makes it hard to predict what a client receives for a small binary download.

Does mod_deflate compress responses smaller than DeflateBufferSize, or pass them through uncompressed?
Which configuration reliably produces Content-Encoding: gzip for small application/octet-stream responses on Apache 2.4?
Is the behavior version-dependent, and where is it documented?

Tasadduq Burney · Answer

Compression and Buffer SizeNo, mod_deflate does not skip compression for responses smaller than the DeflateBufferSize. The DeflateBufferSize directive controls the size of the internal buffer used by the zlib library to process fragments of data; it is not a minimum size threshold for triggering compression.If a response is processed by the deflate filter, it will be compressed and the Content-Encoding: gzip header will be applied, regardless of whether the payload is 10 bytes or 10 megabytes. This behavior is consistent across the Apache 2.4 series and previous 2.2.x releases.Reliably Enabling Gzip for application/octet-streamBecause application/octet-stream is often excluded from default compression lists to avoid double-compressing binary files, you must explicitly instruct Apache to filter this MIME type. To ensure small binary responses are consistently gzipped, use the following configuration:# Enable compression for binary streams
AddOutputFilterByType DEFLATE application/octet-stream

# Optional: Ensure the buffer is tuned for your environment
DeflateBufferSize 8192Alternatively, if you only want this behavior for a specific path, use a <Location> block with SetOutputFilter DEFLATE.Verification StepsTo verify that small payloads are being compressed, you can use curl to inspect the headers of a file smaller than your configured DeflateBufferSize:Request the headers only: curl -I http://your-server/small-file.binConfirm the presence of Content-Encoding: gzip.Verify the payload integrity: curl http://your-server/small-file.bin | gunzip -tPotential Edge CasesIf you find that small responses are still not being compressed despite the above settings, check for these common overrides:BrowserMatch/SetEnvIf: Check if no-gzip environment variables are being set for specific User-Agents.Pre-compressed Content: If the server is configured to serve .gz files directly via mod_rewrite, the deflate filter may be bypassed.Filter Order: Ensure no other output filters are removing the deflate filter or modifying the encoding headers.Missing Diagnostic Detail: Are you using mod_rewrite or mod_headers to manually manipulate the Content-Encoding header elsewhere in your configuration?

Does mod_deflate skip gzip compression for responses smaller than DeflateBufferSize?

1 answer

Compression and Buffer Size

Reliably Enabling Gzip for application/octet-stream

Verification Steps

Potential Edge Cases

Your perspective belongs here.

0 question comments