[squid-users] Exception with squid 3.5.25 in ICAP options path

2018-03-12 Thread Arunabha Saha
Seeing a exception followed by termination fairly regularly with Squid-->Icap with this stacktrace on 3.5.25. The problem typically happens when icap has not been started yet and squid is processing some requests and is configured for ICAP adaptation service. It seems like the ICAP Options

Re: [squid-users] Squid 3.5.25 does not recognise ICAP 408 status code

2018-10-31 Thread Arunabha Saha
Subject line so it is more specific > than "Re: Contents of squid-users digest..." > > > Today's Topics: > >1. > On 10/30/18 6:45 PM, Arunabha Saha wrote: > > > Squid 3.5.25 does not seem to recognise the 408 request timeout error > > code from ICAP

[squid-users] Squid 3.5.25 does not recognise ICAP 408 status code

2018-10-30 Thread Arunabha Saha
Squid 3.5.25 does not seem to recognise the 408 request timeout error code from ICAP. The more troublesome issue for me is the exception it generates and then declares ICAP down after a certain number of such exceptions. I don't want to disable the failure limit entirely given that we can often

Re: [squid-users] squid-users Digest, Vol 59, Issue 10

2019-07-10 Thread Arunabha Saha
>The client will attempt to open a TLS/TCP connection to the origin >server. Your router (or some such) will redirect client TLS/TCP bytes to >your Squid's https_port. If configured correctly, Squid will accept that >TCP connection and wrap/forward it into/inside an HTTP CONNECT tunnel >through

Re: [squid-users] squid-users Digest, Vol 59, Issue 12

2019-07-16 Thread Arunabha Saha
y setup > Message-ID: > <42a9f4e2-8ca2-eb2b-88e9-751d4af75...@measurement-factory.com> > Content-Type: text/plain; charset=utf-8 > > On 7/10/19 7:44 PM, Arunabha Saha wrote: > >> The client will attempt to open a TLS/TCP connection to the origin > >> se