https://bz.apache.org/bugzilla/show_bug.cgi?id=68970
--- Comment #14 from Ruediger Pluem <rpl...@apache.org> --- (In reply to Allan Schrum from comment #10) > > Enter mod_deflate. It wants to change the response of any request (not > necessarily just a CGI response) so that it is compressed to reduce network > load. To do so it must insert itself in the response stream. Within this > conceptual httpd daemon it should be at the output of the daemon acting as > an intermediate client. It reads the HTTP response from the daemon, > compresses it, wraps it with chunked output, and sends it on its way. Using > this conceptual model, with mod_deflate between the Apache httpd daemon and > the client, mod_deflate must properly read the response in order to compress > the response. This might mean de-chunking that response in order for it to > be compressed. Unfortunately your understanding on how this works is wrong. mod_deflate is applied before the HTTP protocol layer. mod_deflate expects a byte stream as input not a HTTP response that can have a transfer encodings applied. Of course mod_deflate interacts with the HTTP protocol by taking care to unset a e.g. Content-Length or Content-MD5 header as they get invalid due to the compression. It also adjusts ETag headers if requested. But the response body is just taken as is and not subject to any dechunking. Hence my question elsewhere for a minimal configuration that demonstrates that this works with mod_deflate prior to 2.4.59. -- You are receiving this mail because: You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org For additional commands, e-mail: bugs-h...@httpd.apache.org
