Hi,
I noticed that squid behaves differently with regard to checking the
SNI of a (fake-)Connect request depending on the sslbump step a
"splice" is performed. This is more or less a follow-up on " Squid
spliced TLS handshake failing with chrome/ium fallback for certain
servers".
If spl
On 18/09/21 8:14 am, Alex Rousskov wrote:
On 9/17/21 3:29 PM, Andreas Weigel wrote:
If splicing at step3, however, hostHeaderVerify is not called again with
the SNI
I assume that the above statement would still be true if I remove the
word "again" from it. This is how I interpreted it (i.e.
h
On 9/17/21 3:29 PM, Andreas Weigel wrote:
> If splicing at step3, however, hostHeaderVerify is not called again with
> the SNI
I assume that the above statement would still be true if I remove the
word "again" from it. This is how I interpreted it (i.e.
hostHeaderVerify() is called once with the
On 9/17/21 10:35 AM, Moti Berger wrote:
> It's possible that in some cases they will run concurrently, however not
> in my setup. The ICAPs are chained. If the chain doesn't guarantee it
> please let me know since I rely on it.
Chaining adaptation services guarantees that they will _start_
sequen
Hi
It's possible that in some cases they will run concurrently, however not in
my setup. The ICAPs are chained. If the chain doesn't guarantee it please
let me know since I rely on it.
Regarding what you said about things that can happen in parallel, I'm OK
with it since what I care the most is t
Dear Squid devs,
thanks for all the work you did to make 5.1 happen!
I’m working with the official repo linked on this wiki page:
https://wiki.squid-cache.org/DeveloperResources to update our
system to Squid 5.1. However, there doesn’t seem to be a tag
corresponding to that release, the latest on
