More info about that "subsequent request" -- it is a history.back() javascript call. But as I said, that fails when we use squid (goes into an infinite loop), but works fine when we use a different proxy (such as Apache mod_proxy or CCproxy) which sends HTTP/1.1 headers. Trying IE7 isn't an option for us right now, so we're discussing internally whether we can fix this with code or if we need to switch to a different proxy. It looks like IE6 is misbehaving here, but there doesn't seem to be a way to fix it. Henrik Nordstrom-5 wrote: > > On fre, 2007-08-24 at 02:15 -0700, ToddWilliams wrote: > >> A subsequent request seems to come from IE6's local cache -- it ignored >> the directives. > > Odd. > > -- View this message in context: http://www.nabble.com/IE6-ignoring-cache-control-due-to-HTTP-1.0-header--tf4322528.html#a12392807 Sent from the Squid - Users mailing list archive at Nabble.com.
