By the help of God.
I'm trying to bypass chat.google.com domain from my squid (with sslbump),
But still no success.
I tried build acl using:
acl bypass url_regex -i chat.google.com
and
acl bypass ssl::server_name_regex -i chat.google.com
And still I can see in the logs that chat.google.com i
On 13.07.23 11:29, Ben Goz wrote:
By the help of God.
so, do you want us to help you or not?
I'm trying to bypass chat.google.com domain from my squid (with sslbump),
But still no success.
I tried build acl using:
acl bypass url_regex -i chat.google.com
and
acl bypass ssl::server_name_reg
On 13/07/23 20:29, Ben Goz wrote:
By the help of God.
I'm trying to bypass chat.google.com domain
from my squid (with sslbump),
But still no success.
I tried build acl using:
acl bypass url_regex -i chat.google.com
and
acl bypass ssl::server_name_regex -i chat.google.com
And still I can
Good day everyone,
We are now trying to move the configuration with was valid and working in Squid
5.7 to Squid 6.1 and hitting the following error:
Unknown authentication scheme 'ntlm'
The problem seem to be with the following configuration we use (output from
squid -k parse).
023/07/13 13:34
Hi Rafael,
that code was moved to a RegisteredRunner in commit
09490bb867d0b3f00a29911a65c715108e95b782 .
I'm not sure why it is not working for you; what is the output of 'squid
-v' to get configure options?
Thanks,
Francesco
On Thu, Jul 13, 2023 at 1:38 PM Rafael Akchurin <
rafael.akchu...@
On 7/13/23 10:29, Francesco Chemolli wrote:
Hi Rafael,
that code was moved to a RegisteredRunner in commit
09490bb867d0b3f00a29911a65c715108e95b782 .
I'm not sure why it is not working for you
That commit broke NTLM support in some environments because the linker
in those environments doe
And the configure options are just those from Debian Unstable (I just added the
--disable-optimizations to be able to debug in vscode):
./configure \
--with-build-environment=default \
--disable-optimizations \
--enable-build-info="ubuntu 22" \
--datadir=/usr/shar
Please see if the following partial fix helps in your environment:
https://github.com/squid-cache/squid/commit/5596a2f4894f80864b660b035d05f5aec74f8312.patch
The fix has been posted for preliminary review as draft PR 1422:
https://github.com/squid-cache/squid/pull/1422
Thank you,
Alex.
On
Hi,
My project makes user-initiated requests to a selection of HTTPS API, I'm
using squid 5.7 as a forward proxy with SSL bumping to aggressively cache
results, and it's working great for that.
One of the API (let's call it 'foobar.org') has a strict 1 request per second
limit. I would like t
