we are using squid a a perimeter egress filter. one think I've recently noticed
is based on my current config it's possible to make a request through squid to
an HTTPS endpoint with out doing a CONNECT request.
I was wondering if this should be allowed behavior for a proxy or if it's just
a bu
I've been trying to get SslBump work for whitelist purposes and so far
have been failing.
It's my understanding in order for SslBump to do whitelist it will
need to do a splice at step2 or step3.
Looking at my logs I see step1 matching but I never see step2. I
believe it's because of what I found
I've been trying to get SslBump work for whitelist purposes and so far have
been failing.
It's my understanding in order for SslBump to do whitelist it will need to
do a splice at step2 or step3.
Looking at my logs I see step1 matching but I never see step2. I believe
it's because of what I found
failing to restart after log rotation
event.
On 10/11/2018 06:30 AM, Joseph Jones wrote:
> I'm trying to find a root cause for failed workers.
My suggestions:
0. Upgrade to the latest Squid v4.
1. Disable memory cache:
cache_mem 0
2. Maintain one cache.log per worker. For
I'm trying to find a root cause for failed workers. We have three squid
instances that act as transparent forward proxies that limit internet
connectivity for our network by doing url whitelisting. Current throughput per
instances is about 90MB/s. after a restart of squid all workers seem to be
