OK so the issue was that:
The http_port was used for ssl bump with intercept while the only port which
can really intercept ssl connections is:
https_port
so I believe that there should be a warning about such a line in the cache log.
When there is http_port and intercept and ssl_bump there
On 2024-08-23 06:29, ngtech1...@gmail.com wrote:
OK so the issue was that:
The http_port was used for ssl bump with intercept
I would not phrase it that way because "bump" is a red herring here. I
would instead say that the issue was that "http_port was used for
intercepted TLS traffic" or "
Hello Squid Support,
We upgraded our Squid Web Proxy from 2.5 to 5.5 recently. After working out a
few issues with backend services and authentication, our client can finally
browse the web and adhere to all of the ACL rules and lists as expected.
The problem we're having now is that we're unab
On 2024-08-23 12:07, Piana, Josh wrote:
The problem we’re having now is that we’re unable to access local
resources on different subnets. For instance, our “main” networks are
10.46.x.x and 10.47.x.x, but the proxy is blocking us when we try to get
to 172.26.x.x as well as 10.96.x.x.
Blocki
