[squid-users] After a Successful PURGE, Still Get TCP-DENIED

[dkovacevic]

I have an external_acl_type directive which returns "OK" or "ERR" depending
on a database query.

The problem is this: when the database is updated, which should permit the
site to be accessed, Squid has the previous response cached, the result
being continued "access denied" responses until either Squid is restarted or
the result expires (where?).

I attempted to clear the cache by using PURGE request via squidclient, which
is successful in clearing the cache, but not the result decision
(TCP-DENIED). After running the PURGE, doing a refresh in browser causes
another lookup in Squid- but Squid then returns "access-denied" (no database
query).

What do I need to do to force Squid to check the ACL after a browser
refresh?





--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/After-a-Successful-PURGE-Still-Get-TCP-DENIED-tp4668699.html
Sent from the Squid - Users mailing list archive at Nabble.com.