Thank you for the reply. Thank you for confirming that the connections that are
started are not effected by the last ACL, thus clients not on acls prior would
be blocked and not allowed to access the cache. However ones that are would be
able to use the cache.
Jonathan Lee
Adult Student
Sent
On 24/04/24 17:27, Jonathan Lee wrote:
Hello fellow Squid users I wanted to ask a quick question for use with
termination would http access for cache still work with this type of setup and
custom refresh patterns?
I think it would terminate all but the clients and if they use the cache it
Hello fellow Squid users I wanted to ask a quick question for use with
termination would http access for cache still work with this type of setup and
custom refresh patterns?
I think it would terminate all but the clients and if they use the cache it
would be ok.
But I think an invasive
On 23/04/24 11:52, Jonathan Lee wrote:
Hello fellow Squid Accelerator/Dynamic Cache/Web Cache Users/PfSense users
I think this might resolve any container based issues/fears if they
happened to get into the cache. Ie a Docker Proxy got installed and
tried to data marshal the network card
correction use both acl for and use
> ssl_bump peek step1
> miss_access deny no_miss
> ssl_bump splice https_login
> ssl_bump splice splice_only_mac splice_only
> ssl_bump splice NoBumpDNS
> ssl_bump splice NoSSLIntercept
> ssl_bump bump bump_only_mac bump_only
> ssl_bump terminate all # if its
Hello fellow Squid Accelerator/Dynamic Cache/Web Cache Users/PfSense users
I think this might resolve any container based issues/fears if they happened to
get into the cache. Ie a Docker Proxy got installed and tried to data marshal
the network card inside of a freeBSD jail or something like
