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=19954>. 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=19954 [PATCH] HTTP tunneling through reverse proxy does not always work ------- Additional Comments From [EMAIL PROTECTED] 2003-12-10 11:17 ------- The logic to hold on to output until we get 8K is not intended to be caching behavior, but instead to send out full packets so that we don't abuse the network. But if we don't pass flush buckets down at the right time, it breaks some applications that need to send output to the client a piece at a time. A flush bucket should be passed down when we've read some output but we find out that another read would block. At this point it is safe to assume that the CGI/origin-server/whatever is not going to generate more output for a while and the output generated so far should be flushed to the client. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
