On 21/09/17 22:16, kAja Ziegler wrote:
Thats what the "must-revalidate" means. It should work better with
just max-age or Expires header - and with a longer value than 60 sec
since this is supposed to be a *permanent* situation.
As I know "must-revalidate" mean "refuse to return stale responses to
the user even if they say that stale responses are acceptable" - cached
object must be revalidated.
Max-age=60 was only used for testing.
The results of my testing:
- redirect 302 or 307 - to be cached needs Cache-Control max-age > 0 or
Expires "access plus 1 seconds"
- redirect 301 - to be cached needs Cache-Control max-age > 60 or
Expires "access plus 61 seconds"
There is no >60 need on the 301. Just me suggesting that 60sec is too
short caching time for a _permanent_ thing.
This is strange because I thought that 301 is always cached without
Cache-Control or Expires headers. And I can't find any information in
the documentation which describes such behaviour.
It should be, so long as it is fresh so that means it does depend on
refresh_pattern saying it is fresh when no controls are present.
Amos
_______________________________________________
squid-users mailing list
squid-users@xxxxxxxxxxxxxxxxxxxxx
http://lists.squid-cache.org/listinfo/squid-users
