On 11/19/2016 02:15 AM, Amos Jeffries wrote:
> On 19/11/2016 12:56 p.m., Eduard Bagdasaryan wrote:
>> This patch introduces a new 'auth_schemes' squid.conf directive.
>>
>> This directive may be used to customize authentication
>> schemes presence and order in Squid's HTTP 401 (Unauthorized) and
On 11/19/2016 07:06 PM, Amos Jeffries wrote:
> On 20/11/2016 12:08 p.m., Marcus Kool wrote:
>> The current ssl bump steps allow problematic configs where Squid
>> bumps or stares in one step and to splice in an other step,
>> which can be resolved (made impossible) in a new configuration syntax.
On 11/19/2016 03:07 AM, Amos Jeffries wrote:
> I propose going back to the older config style where each step has its
> own directive name which self-documents what it does.
IIRC, SslBump has never used step-specific directives: First
implementations applied all ssl_bump actions during step1 and
http://build.squid-cache.org/job/5-matrix/compiler=gcc,label=d-debian-unstable/23/--
[...truncated 34484 lines...]
../../../../src/ssl/support.cc:473:96: error: invalid conversion from 'int
(*)(CRYPTO_EX_DATA*, CRYPTO_EX_DATA*, void*, int, long int, void*)
On 17/11/2016 3:43 a.m., Garri Djavadyan wrote:
> Dear developers,
>
> Please review the attached patch for Squid-5 fixing the issue explained
> in the bug report 3290 [1]. The issue is still reproducible using rev.
> 14947.
>
> The problem exists because Squid resets expiration time for a user
