DO NOT REPLY [Bug 18157] New: - Proxy Buffering Disrupts Staged Response Delivery

[bu...@apache.org]

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=18157>.
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=18157

Proxy Buffering Disrupts Staged Response Delivery

           Summary: Proxy Buffering Disrupts Staged Response Delivery
           Product: Apache httpd-1.3
           Version: 1.3.27
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Minor
          Priority: Other
         Component: mod_proxy
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: gavin@eleventeenth.com


Using mod_proxy as a reverse proxy we discovered that buffering was collecting
staged "update" messages for a long lived process and delivering several at
once.  This disrupted the response as it was staged to give updates to the
browser to keep the connection alive, preventing a "Document contains no data"
type error.

The problem was tracked to the fact that mod_proxy's ProxyIOBufferSize ignores
values less than 8192 bytes, also ap_bwrite in buff.c will buffer responses when
using mod_proxy.

I have a patch to allow less than 8192 in ProxyIOBufferSize and to allow the
presence of a "X-Buffer-Output" header set to "no" to unset the B_WR flag in the
response to the browser.  I will attach this patch as an update to this bug.

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