On Sun, May 05, 2002 at 02:56:02PM -0400, Joshua Slive wrote: > Just to start, what about HTTP/1.0 clients? Even for HTTP/1.1 clients, > it seems chunked encoding should only be used when necessary. Chunked > encoding is extra overhead, and removes information that may be valuable > down-the-line. We don't send chunked encoding for ordinary static > content when we are the origin server, do we?
Nope, we let our normal logic takeover - we don't do anything special. If our client can't handle it (i.e. 1.0 client), then the server adjusts accordingly. It will be treated just like any other served page (as far as our output filters are concerned). Whatever logic we use to handle chunking or keepalives or whatever are just reused with proxy as with any other page we serve. There is logic in the output filters for determining when to do chunked encoding. This is entirely separate from the proxy code. In fact, httpd-2.0 is much more prone to using chunked encoding than 1.3 ever was. What decision the proxy server made for C-L or encoding should have no impact on what we do for our client (imagine using mod_deflate in conjunction with proxy). IMHO, proxy is especially good for chunked encoding, because we read the proxy and if we use chunks on the output, we can return the data sooner than waiting for the entire response to be read before writing anything to the network. -- justin
