It's not clear if only Chromium or also a simple Chrome.
Thanks,
Eliezer
Eliezer Croitoru
Tech Support
Mobile: +972-5-28704261
Email: ngtech1...@gmail.com
Zoom: Coming soon
-Original Message-
From: squid-users On Behalf Of
Dieter Bloms
Sent: Wednesday, January 20, 2021 1:26 PM
To
-grecord-gcc-switches -pipe -Wall -Werror=format-security
-Wp,-D_FORTIFY_SOURCE=2 -Wp,-D_GLIBCXX_ASSERTIONS
-specs=/usr/lib/rpm/redhat/redhat-hardened-cc1 -fstack-protector-strong
-specs=/usr/lib/rpm/redhat/redhat-annobin-cc1 -m64 -mtune=generic
-fasynchronous-unwind-tables -fstack-clash-
Hello Eliezer,
I've tested with chrome 87.0.4280.141 and Edge 87.0.664.75.
On Wed, Jan 20, Eliezer Croitoru wrote:
> It's not clear if only Chromium or also a simple Chrome.
>
> Thanks,
> Eliezer
>
>
> Eliezer Croitoru
> Tech Support
> Mobile: +972-5-28704261
> Email: ngtech1...@gmail.com
The config you have is doing client-first bumping (bump at step). It happens before the real cert or server details are available. As such any number of TLS features or extensions may be missing (or added) by squid that indicate problems to the browser.If you can use a config the peek/stare/splice
