[Bug 52879] mod_proxy_fcgi wrong behavior with 304

[bu...@apache.org]

https://issues.apache.org/bugzilla/show_bug.cgi?id=52879

--- Comment #5 from Luke G. <sp...@gmail.com> ---
The patch r1331416 introduced a serious bug: 

In the case described by the original poster (a PHP script run as fastcgi
through php-fpm and mod_proxy_fcgi which returns a Last-Modified header with no
Status header), Apache does indeed now return a 304 status (if a matching
If-not-modified header is in the request) BUT the content of the php script is
also sent. 

This breaks the http protocol as described in rfc2616 section 10.3.5: "The 304
response MUST NOT contain a message-body, and thus is always terminated by the
first empty line after the header fields."

This cause us a serious problem when this kind of request is sent through our
reverse proxy placed just in front of the backends. When the proxy receives
this (invalid) 304 response, it immediately sends a 304 to the client and
ignores the rest of the packet; but the next packets sent by the backend stay
in the tcp stack (the proxy does not expect further content). The reverse proxy
prepends these packets in the response to the next request routed to the same
backend. This, of course, breaks our applications...

Can someone suggests a patch we could test to fix this problem?

-- 
You are receiving this mail because:
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org