(Resending, first time accidentally sent with HTML formatting, bounced)
Now I see the Expires header having a value in the past, which may
confuse clients and caches further down the chain.
Scenario: origin returns max-age=900 (15 min) and refresh_pattern
overrides expire to 24 hours, what do the
ons 2009-09-02 klockan 12:42 -0700 skrev Guy Bashkansky:
Now I see the Expires header having a value in the past, which may
confuse clients and caches further down the chain.
Scenario: origin returns max-age=900 (15 min) and refresh_pattern
overrides expire to 24 hours, what do the headers to
ons 2009-09-02 klockan 13:42 -0700 skrev Guy Bashkansky:
I'm using a customized version of Squid 2.4 STABLE6. But nothing
seems to be customized in refresh.c, except for my own recent swap of
age and expires checks (as recommended).
Ouch.. that's a very very old relese. Upgrading highly
ons 2009-08-26 klockan 18:17 -0700 skrev Guy Bashkansky:
If indeed refresh_pattern only extends expiration, I would like to
develop a feature that enforces an exact time-to-live (per URL) in my
local branch of Squid code.
See the refreshStaleness() function. Should be sufficient to move the
I've tried to set an exact time-to-live (override origin cache
control) in Squid (2.4 STABLE6) configuration by refresh_pattern,
e.g.:
refresh_pattern 30_minutes_cache_control_url 15 0% 15
override-expire ignore-max-age
Observed: URL is matched (in log), but objects still cached for 30
