On 31/10/02 14:36 "Martin Algesten" <[EMAIL PROTECTED]> wrote:
> 1. Tomcat should either not send any headers on a 304, or if it does > then make sure that they do reflect the correct values for the requested > object (e.g. not call a gif a text). > > 2. Not entirely sure here. Reading the HTTP/1.1 > http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.5 > It states: > "If a cache uses a received 304 response to update a cache entry, the > cache MUST update the entry to reflect any new field values given in the > response." > > I suspect that is what we're seeing in mod_proxy. But I just realised > that I have some reading to do, the stuff about weak and strong > validator didn't make much sense to me... I too believe that mod_proxy is behaving quite correctly according to the spec... Tomcat should not send those headers... It will also impact client (browser) caches, not only mod_proxy... Pier -- To unsubscribe, e-mail: <mailto:tomcat-dev-unsubscribe@;jakarta.apache.org> For additional commands, e-mail: <mailto:tomcat-dev-help@;jakarta.apache.org>
