> > The proxy should flush, because otherwise the data won't stream to
the
> > client.
>
> doesn't the core flush once it has max-something bytes or eos?
Only if the data makes it to the core_output_filter. :-)
> > The problem that I see, is that the proxy shouldn't be removing
> > the C-L fr
At 11:43 PM 4/4/2002, rbb wrote:
>The problem that I see, is that the proxy shouldn't be removing
>the C-L from the response that the origin server provided.
>
>If you can get a C-L by removing the flush bucket, then the C-L filter
>is the thing providing the header data. But, we have a C-L from
On Thu, 4 Apr 2002, Ryan Bloom wrote:
> The proxy should flush, because otherwise the data won't stream to the
> client.
doesn't the core flush once it has max-something bytes or eos?
> The problem that I see, is that the proxy shouldn't be removing
> the C-L from the response that the origin s
> mod_proxy does not send a Content-Length header, seems because of the
> flush bucket inserted by ap_proxy_http_process_response()
>
> if i break in ap_content_length_filter, when a request is handled by
> default_handler, brigade looks like so:
> (gdb) dump_brigade b
> dump of brigade 0x8235318
mod_proxy does not send a Content-Length header, seems because of the
flush bucket inserted by ap_proxy_http_process_response()
if i break in ap_content_length_filter, when a request is handled by
default_handler, brigade looks like so:
(gdb) dump_brigade b
dump of brigade 0x8235318
0: bucke
