On 05/08/2017 12:49 AM, Amos Jeffries wrote:
>
> On 08/05/17 13:18, Alex Rousskov wrote:
>> On 03/31/2017 07:21 AM, Christos Tsantilas wrote:
>>> Avoid sending second CONNECT request to adaptation
>>>
>>>
>>> The users may not want to send the s
On 08/05/17 13:18, Alex Rousskov wrote:
On 03/31/2017 07:21 AM, Christos Tsantilas wrote:
Avoid sending second CONNECT request to adaptation
The users may not want to send the second request to the adaptation
services. In this case they can
On 03/31/2017 07:21 AM, Christos Tsantilas wrote:
> Avoid sending second CONNECT request to adaptation
>
>
> The users may not want to send the second request to the adaptation
> services. In this case they can use acls as follows:
>
> acl step
Applied as r15121 to squid-5 branch.
On 14/04/2017 02:02 μμ, Amos Jeffries wrote:
On 14/04/2017 1:10 a.m., Christos Tsantilas wrote:
If there are not objections I will apply this patch to squid-5 branch
I'm not seeing anything obviously wrong with it and its past the 10-day
criteria. So sur
On 14/04/2017 1:10 a.m., Christos Tsantilas wrote:
> If there are not objections I will apply this patch to squid-5 branch
>
I'm not seeing anything obviously wrong with it and its past the 10-day
criteria. So sure, apply away.
Amos
___
squid-dev mail
If there are not objections I will apply this patch to squid-5 branch
On 31/03/2017 04:21 μμ, Christos Tsantilas wrote:
Hi all,
Squid does not send CONNECT request to adaptation services if the
"ssl_bump splice" rule matched at step 2. This adaptation is important
because the CONNECT request g
Hi all,
Squid does not send CONNECT request to adaptation services if the
"ssl_bump splice" rule matched at step 2. This adaptation is important
because the CONNECT request gains SNI information during the second
SslBump step. This is a regression bug, possibly caused by the Squid bug
4529 fi
