Sorry, I haven't seen the reply as it's been attached as an attachment and
posted a similar question about 302, but probably I know the answer already
as it's not stateful inspection any redirection to a new domain is a new
request that has to go over ACL again. I thought about using
http_reply_acc
There is a built-in ACL called "all" which does what you defined for the regex "blacklist" to do.As for sessions. No Squid follows HTTP which is stateless. You can configure it though. setup an ext_session_acl helper for active mode sessions that start when a 302 response comes back. you should hav
I've found a resolution using a bit better regex:
acl blackList url_regex ^https?:\/\/.*$
looking at the debug it doing exactly what I wanted, however, I now have a
different issue how to handle a 302 MOVED when the move is to a different
domain, e.g. packages.gitlab.com are moved to d20rj4el6vkp
Hi,
I'm trying to use Opnsense built-in squid config to set up a transparent
proxy for server updates and block everything else.
In GUI they use url_regex for whitelist and blacklist, when I simple per
domain whitelist and blacklist it's working as expected, e.g.
# ACL - Whitelist - User defined (
