Brian Akins wrote: > > Jim Jagielski wrote: > > > Hmmm. I haven't taken a look yet, but is seems to me that > > only complete responses should be cached, not partial, and > > as such we need some better mechanism in place for that > > "Not Cache-able", "Could be Cache-able" and "To-Be-Cached" > > state tree. > > > > From the best I can tell, the issue is in the proxy code. When a > response gets "truncated" for whatever reason, it doesn't pass an error > along, so the filters never know that "something bad" happened. >
Yep... a prelim look indicates that any error within the proxy isn't bubbled down (or is it up? :) ) to the cache (or almost anthing else ;) ). -- ======================================================================= Jim Jagielski [|] [EMAIL PROTECTED] [|] http://www.jaguNET.com/ "If you can dodge a wrench, you can dodge a ball."
