Ah. That being an old version may be part of your problem. 3.1 only
supports ~60% of HTTP/1.1 requirements.
I have spent some time trying to build 3.5.15 from source and install it on Red Hat, hoping it would resolve the caching issue. It builds fine, but I'm having permission issues with the log file that are probably caused by SELinux. Any pointers would be appreciated.
> I had read that "Cache-Control: no-cache" indicates that caching should not
> be used to satisfy requests, but that "Cache-Control: max-age=0" only
> indicates that *client* caching should not be used. Is this not the case?
You don't have "no-cache" in those log entries. Your particular old
Squid version does not fully support no-cache subtle details anyway. So
it treats no-cache as if it were no-store.
Yes, agreed, no-cache is not specified. I was trying to differentiate between the no-cache behavior and max-age=0 behavior.
You have Q-CC values of max-age=0. That is called "reload" in HTTP
terminology. The client overridding the REP-CC values and demanding that
the copy it gets given is no more than 0 seconds old. ie. forcing Squid
to fetch new data (MISS).
Are you saying that Chrome (and I have done some further testing and determined that Safari is acting the same way) is demanding that a cached value, if one exists, not be returned? So the lack of returning a cached value is to be expected? Why would the browser be demanding that? What controls whether a browser sets "max-age=0"? Again, my reading seemed to indicate that "max-age=0" should only control client side caching, not server side caching.
You can use the 'reload-into-ims' parameter on refresh_pattern rules to
make Squid 'reload' using a revalidation request when that pattern
matches. I think that will turn the Chrome actions into what IE is doing
below.
Could you please give me an example of what that line would look like?
Reading the squid documentation, it appears that the 'reload-into-ims' is dangerous and not recommended. Is there a more compliant way of providing the desired caching behavior?
Thanks,
Cindy
_______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
