|
Home > Archive > Squid > May 2004 > [squid-users] Is it worth caching .html files?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
[squid-users] Is it worth caching .html files?
|
|
| Jason McNeil 2004-04-30, 12:38 pm |
| Hi there I've had some recent complaints from users about receiving
stale pages despite hitting their reload/refrsh buttons. I know myself
to press and hols shift and reload to solve the problem, but I don't
expect my users to as well. I guess my real question here is, is it even
worth caching .html files? Normally squid will have to contact the
target server to ask for a fresh copy anyways, and with the relatively
small size of html files it would probably not make much difference if
they were never cached at all, but the user would still graphics and
other objects from the cache.
Should I put this in?
< acl FRESHPAGES urlpath_regex cgi-bin \? (html|shtml)
< no_cache deny FRESHPAGES
yay or nay?
| |
| Henrik Nordstrom 2004-05-01, 12:36 pm |
| On Fri, 30 Apr 2004, Jason McNeil wrote:
> Hi there I've had some recent complaints from users about receiving
> stale pages despite hitting their reload/refrsh buttons.
Are you doing transparent interception? If you have make sure to have the
browser configured to use the proxy.
If you do have the browser configured to use the proxy then make sure the
clock of the proxy server is reasonably correct.
You are only supposed to need to do a "Shift+Reload" in the unlikely event
that the clock of the origin server suddenly goes backwards.. but if you
are transparently intercepting port 80 then the browsers does not know
about the cache and does not always indicate "reload" when the reload
button is used (without Shift+Reload).
Regards
Henrik
|
|
|
|
|