[resent to varnish-misc]
Sascha Ottolski [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
If you know the exact URL to purge, use an HTTP PURGE (see VCL code
examples in the vcl man page)
I'm aware of this, but had expected that the semantic of both method
would be
Sascha Ottolski [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
No, the semantics are completely different. With HTTP PURGE, you do
a direct cache lookup, and set the object's TTL to 0 if it exists.
With url.purge, you add an entry to a ban list, and every time an
Am Montag 14 April 2008 14:19:11 schrieb Dag-Erling Smørgrav:
Sascha Ottolski [EMAIL PROTECTED] writes:
Dag-Erling Smørgrav [EMAIL PROTECTED] writes:
No, the semantics are completely different. With HTTP PURGE, you
do a direct cache lookup, and set the object's TTL to 0 if it
exists.
Hi,
I just needed to get rid of about 27,000 stale URLs, that were cached as
404 or 302 due to a configuration error on the backends.
So I did a url.purge in a loop, sleeping 0.1 seconds after each URL:
for i in `cat notfound.txt.sorted` ; do varnishadm -T:81 url.purge $i;
sleep 0.1; done
