https://bz.apache.org/bugzilla/show_bug.cgi?id=68970
Joe Orton <jor...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|mod_deflate |mod_cgi
--- Comment #11 from Joe Orton <jor...@redhat.com> ---
mod_deflate has nothing to do with this AFAICT. A CGI script producing T-E:
chunked output will fail in the way you describe with or without mod_deflate
configured.
mod_deflate applies a content-coding to the CGI output and this is done
trivially without the CGI script output needing to use HTTP/1.1 message
framing. This is even covered in
https://datatracker.ietf.org/doc/html/rfc3875#section-6.4
> Apache httpd should leave it alone and simply send it back without touching it
You can interpret this quite literally for 2.4.59+ - the CGI response is read
until EOF (as described in the CGI spec) and that response body is exactly what
the client will read, with appropriate HTTP message framing applied.
> This different interpretation on how CGI works seems against the standard
Please can you be specific - which standard, in what way?
FWIW - a CGI script unconditionally producing T-E: chunked output will also
definitely violate HTTP/1.0 since 1.0 clients cannot parse chunked
transfer-coding. This is why it is appropriate for httpd to handle the HTTP
message framing, not the CGI script.
--
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
