- From: A Bagi <ahmed.bagi@virgin.net>
- Date: Mon, 5 Jan 2004 16:41:05 -0000
- To: "Mark Nottingham" <mnot@mnot.net>, <anzenews@volja.net>
- Cc: <www-talk@w3.org>
It maybe an idea to reiterate those basic factors we all learnt at college! Data is primarily sorted in the cache (how many hits provides hit-rate and so on). If the data is 'frequently' stored and implemented, systems would then use smart caching. There is however a world of complexities on which information is repeatedly kept/used! Ahmed ----- Original Message ----- From: "Mark Nottingham" <mnot@mnot.net> To: <anzenews@volja.net> Cc: <www-talk@w3.org> Sent: Monday, January 05, 2004 4:33 PM Subject: Re: IE6 and Cache-Control headers > > Cache implementations are not *required* to cache things when they're > cacheable; they're only required to not cache them when they're > uncacheable. Some browser cache implementations (not just IE) are quite > simplistic and/or conservative, so they may not cache a lot of things > that other caches will. > > Cheers, > > > On Jan 4, 2004, at 7:44 AM, Anews wrote: > > > Now: other browsers (Opera, Konqueror and Mozilla for Linux) obey and > > check > > the server for newer versions, yet they allow me to issue 304 response > > - the > > way it should be. But IE6 just doesn't cache the response. The weird > > thing is > > that it works as expected on my production server (over LAN), but not > > over > > Internet. > > > > Am I missing something? I tried "Cache-Control: private" too, but to no > > avail... > > > >
Received on Monday, 5 January 2004 11:41:57 UTC