Volodymyr Kostyrko wrote:
Chris Robertson wrote:
Volodymyr Kostyrko wrote:
Chris Robertson wrote:
Obviously the object has changed, so you have a few options:
* Use the PURGE method with squidclient
That's a onetime shooter. This file is requested daily, so I should
run it daily to keep it current.
Is this file changed daily?
Yep. Sometimes faster.
* force a refresh with your browser (hold down shift or control when
you press the refresh or reload button, use the -r switch with
squidclient or --cache=off for wget. fetch does not appear to have
a method of forcing a refresh.)
Worked. Same problem - results ain't persistent.
* Add a cache deny for this domain
Thinking of it.
* Wait for the freshness calculation to expire (3 days at the most)
And? The file already stuck in cache for 2 month. Waiting some more
days does literally nothing.
The default refresh_patterns will not keep an object (without expiry
information) cached for more than three days.
I'm just curios, maybe some other headers can trigger that? Like
negative ETag?
I'm just trying to understand is this some flaw in my config or it
just should work this way.
It should not work this way by default... Share your config, and
perhaps we can help find the cause.
Attached.
You may wish to disable htcp support, it dumps core on SQUID3.0.PATCH8...
Aug 27 10:32:45 utwig squid[34112]: Squid Parent: child process 44700
started
Aug 27 10:36:42 utwig kernel: pid 44700 (squid), uid 100: exited on
signal 8 (core dumped)
Aug 27 10:36:42 utwig squid[34112]: Squid Parent: child process 44700
exited due to signal 8
I'm just looking at it, seems to be some problem in response handling.
Do you mean the If so I'd definitely like to see what you can come up
with about it.
We also have Benno Rice as a new developer looking into code parity and
upgrades for HTCP on Squid-2 and Squid-3.
Amos
--
Please use Squid 2.7.STABLE4 or 3.0.STABLE8
