Bill Stoddard wrote: > Haven't thought this through, but there is at least one complicated case to consider >and > handle correctly. If the backend is chunking a response back to the proxy and that > response exceeds the size the proxy is allowed to cache, then the proxy would need to > abort the caching, send the partial cached file, cleanup that file, then continue >reading > from the backend. And would we want to make this behaviour configurable? Are there > practicle (non-contrived) cases where it is unacceptable to defer sending bytes to >the > client?
In the default design (I dunno if this has been changed) only responses
with content-lengths were able to be cached for this reason.
Regards,
Graham
--
-----------------------------------------
[EMAIL PROTECTED] "There's a moon
over Bourbon Street
tonight..."
smime.p7s
Description: S/MIME Cryptographic Signature
