https://issues.apache.org/bugzilla/show_bug.cgi?id=17629
Jelmer Jellema <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #29 from Jelmer Jellema <[email protected]> 2009-03-10 06:19:54 PST --- Hi, Is there any chance this issue will get fixed in a new mod_filter implementation? mod_deflate (or any FilterChain with more than one filter) is now unusable to anyone who does not know in advance if some of the processing will require subrequests. By the way, in httpd 2.2.3, when a file is run through mod_include containing a subrequest, and afterwards through mod_deflate, the output will not be mixed gzipped/ non-gzipped, but will be not compressed. The only problem now is, that mod_deflate still adds the Content-Encoding: gzip, which confuses the client... So this html-file: --- <html> <body><!--#include virtual="/output.cgi"--></body> </html> ----- and this output.cgi file: --- #!/bin/bash echo 'Content-Type: text/html' echo '' echo 'This is the output' --- Will be delivered, when ran through mod_include and mod_deflate as: ------ HTTP/1.1 200 OK Date: Tue, 10 Mar 2009 13:18:05 GMT Server: Apache Accept-Ranges: bytes Vary: Accept-Encoding Content-Encoding: gzip Connection: close Content-Type: text/html This is the output </body> </html> ----- As you can see: the body is not encoded. (and there isn't even a redirect in the cgi, it is run through a handler and just outputs the content). Jelmer -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
