Just to answer my own question for the archive.
My squid was of course running on the external
class C address and therefore my 'localhost'
(internal class C) acl was not relevant. I added the line:
http_access allow purge server.pl
(acl server.pl src 213.C.C.C/32 was already there)
purge now works no problemo.
cheers,
Mike
> I'm trying to use the purge utility
> (http://www.cache.dfn.de/DFN-Cache/Development/Purge/)
> to purge some mp3 files from a squid 2.4 instance (accel mode)
>
> server:/tmp/purge# ./purge -c
> /usr/local/squid-2.4-delaypool/etc/squid-friko.conf -e '\.mpeg$' -v -p
> server.pl:80 -P1
>
> This gives me a 403 return code
>
> /export/home/cache/squid/00/01/00000133 403 579011
> C2D9349AB0D80E949BAEAC08879034B8 3b55a567
> 3b55a569 ffffffff 3b3836cb ffff 65535 http://dom.pl/usera/film01.mpeg
>
> and a TCP_DENIED:NONE message in my access.log:
> A.B.C.D - - [19/Jul/2001:16:58:39 +0200] "PURGE
> http://dom.pl/usera/film01.mpeg HTTP/1.0" 403 1099 TCP_DENIED:NONE
>
> squid.conf has:
>
> acl purge method PURGE
> http_access allow purge localhost
> http_access deny purge
>
> stracing the server process reveals this is an acl problem, but
> that's about as much detail as I can get.
>
> I can see no hole in my acl. I'm running the purge both as root and as
>
> squid and I get the same result (user squid owns all the cache
> structure). I even hashed out the http_access deny purge line - still
> no joy.
>
> I'm probably missing something daft...
>
> cheers,
> Mike
>
>
>
>
-- Onet.pl S.A. http://www.onet.pl/ Krakow, PolandReceived on Fri Jul 20 2001 - 02:35:06 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:01:17 MST