https://bz.apache.org/bugzilla/show_bug.cgi?id=68970

--- Comment #10 from Allan Schrum <allan.sch...@oracle.com> ---
This different interpretation on how CGI works seems against the standard. The
httpd daemon, when processing a request that is answered by a CGI process,
handles all the networking and connection management, setup up the CGI
environment, and hands off the processing of the request to the CGI process.
The CGI process is required to return a sane response with message headers and
message body. The response is sent back to the client with the daemon
responsible for any transport translation as necessary. In this example the CGI
response is following the standard and returning a set of headers that
identifies the content for an HTTP response. Apache httpd should leave it alone
and simply send it back without touching it. Had that happened there would not
be a problem.

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.

With 2.4.59 that is not what is happening. The output of the CGI process has
all its headers thrown away so that the content cannot be processed. Those
headers are part of the CGI response and are allowed by standard. I don't
understand why years of processing these types of responses suddenly must treat
Transfer-Encoding as something magical to be disregarded.

-- 
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

Reply via email to