Re: [squid-users] Issues with SSLBumped high traffic forward caching

2021-06-10 Thread Matthias Saou
On Wed, 9 Jun 2021 10:45:40 -0400 Alex Rousskov wrote: > > assertion failed: Transients.cc:221: "old == e" > > This is a Squid bug. Please consider creating a Bugzilla entry and > posting the corresponding backtrace there: > https://wiki.squid-cache.org/SquidFaq/BugReporting#crashes_and_core_dum

Re: [squid-users] Squid spliced TLS handshake failing with chrome/ium fallback for certain servers

2021-06-10 Thread Andreas Weigel
Hi Alex, I can only suggest to either fix the Squid bug/limitation or decide to splice during step1 (based on client SNI, etc., before Squid talks to the origin server). don't know why I haven't yet had the idea, but indeed, if I force splicing at step 1 or even 2, the site loads without err

Re: [squid-users] Squid spliced TLS handshake failing with chrome/ium fallback for certain servers

2021-06-10 Thread Alex Rousskov
On 6/10/21 11:00 AM, Andreas Weigel wrote: >> I can only suggest to either fix the Squid bug/limitation or decide to >> splice during step1 (based on client SNI, etc., before Squid talks to >> the origin server). > don't know why I haven't yet had the idea, but indeed, if I force > splicing at st

Re: [squid-users] Squid spliced TLS handshake failing with chrome/ium fallback for certain servers

2021-06-10 Thread Andreas Weigel
Hi again, I can only suggest to either fix the Squid bug/limitation I found Ssl::PeekingPeerConnector::noteNegotiationError in src/PeekingPeerConnector.cc. There are some checks for the case that srvBio->bumpMode() == Ssl::bumpPeek. If I apply the attached patch, matching on the ssl_lib_