https://bz.apache.org/bugzilla/show_bug.cgi?id=68970
--- Comment #17 from Allan Schrum <[email protected]> --- You arguments indicate that you believe this should never have worked. Fine, I accept that. However, it did work for a very long time and it is now broken. Perhaps this worked because previously the code treated the output from CGI as a transfer hop so Transfer-Encoding worked as Apache read the output from the CGI process. It was mentioned that the code change that "broke" this now clears the transfer encoding variable arbitrarily. Perhaps it should only be cleared if Content-Length is provided? So it seems like the options are: 1. Go back to the previous behavior for mod_deflate so that the chunked output from the CGI script is properly read as part of the activities of mod_deflate. 1.a. This might need to be more generic and apply to anything reading the output of the CGI process, not simply mod_deflate. 1.b. Basically, revert the code change. 2. Declare victory as Apache httpd is now finally following the standard(s) 3. Disable mod_deflate 4. Convert our CGI processes to be NPH The NPH approach is odd because its existence means that the standard CGI response does have headers which are parsed by the daemon. If this worked previously because the output of the CGI process was treated as a transfer hop so that the Transfer-Encoding header was parsed and understood by the daemon, I'd prefer we go back to that behavior. It is clean, simple, and still fits within the concepts of CGI. -- 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]
