DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8597>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8597
http_protocol.c doesn't handle chunked transfer encoding right
Summary: http_protocol.c doesn't handle chunked transfer encoding
right
Product: Apache httpd-2.0
Version: 2.0.35
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: mod_proxy
AssignedTo: bugs@httpd.apache.org
ReportedBy: brian@brian-web.com
The http input filter in http_protocol.c doesn't correctly handle responses
using the chunked transfer encoding. It doesn't read the CRLF after the
"0" chunk that terminated the response. This is not a problem except
when a keepalive connection is being used. That last CRLF is read as the
first line of the next response which caused all kinds of problems for
mod_proxy.
On the first request of a page through mod_proxy the page will return
properly, on the next (if a keepalive connection is in use) it will read the
CRLF as the first line of the response and fail. The next load after that will
reconnect and it will then work again. So responses using chunked
transfer encoding end up working through mod_proxy every other time.
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8597>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8597
http_protocol.c doesn't handle chunked transfer encoding right
Summary: http_protocol.c doesn't handle chunked transfer encoding
right
Product: Apache httpd-2.0
Version: 2.0.35
Platform: All
OS/Version: All
Status: NEW
Severity: Normal
Priority: Other
Component: mod_proxy
AssignedTo: bugs@httpd.apache.org
ReportedBy: brian@brian-web.com
The http input filter in http_protocol.c doesn't correctly handle responses
using the chunked transfer encoding. It doesn't read the CRLF after the
"0" chunk that terminated the response. This is not a problem except
when a keepalive connection is being used. That last CRLF is read as the
first line of the next response which caused all kinds of problems for
mod_proxy.
On the first request of a page through mod_proxy the page will return
properly, on the next (if a keepalive connection is in use) it will read the
CRLF as the first line of the response and fail. The next load after that will
reconnect and it will then work again. So responses using chunked
transfer encoding end up working through mod_proxy every other time.