Re: IE not sending correct refresh header?

Jon Drukman writes:
...
> >Has anyone ran into this problem before?
>
> interesting. i'm having the opposite problem: if i reload an object that
> should come from the cache, netscape doesn't seem to care, and causes squid
> to talk to the origin server again, whereas if I use IE it works properly.

Might that be your problem right there, in how you're testing? If you
use the "reload" button, the correct behavior defined by the standard
*is* for the proxy to never use the cached copy, and to fetch it again
from the origin server. I think there is a squid.conf setting to
override this, but you probably don't want to use it, or your site
viewers might be unable to get a new version of your site when you
update.

Instead of using reload, try testing the proxy by using browsers on two
separate computers - the first one loading an image should cause the
proxy to hit the origin server, the second one loading the same image
should fetch it out of memory. Alternatively, closing the browser, and
then opening it on the same page should work the same way.

  -- Clifton

-- 
 Clifton Royston  --  LavaNet Systems Architect --  cliftonr@lava.net
        "An absolute monarch would be absolutely wise and good.  
           But no man is strong enough to have no interest.  
             Therefore the best king would be Pure Chance.  
              It is Pure Chance that rules the Universe; 
          therefore, and only therefore, life is good." - AC