Re: [squid-users] Default state for the option generate-host-certificates

2016-10-29 Thread Amos Jeffries
On 29/10/2016 8:18 a.m., Garri Djavadyan wrote: > On 2016-10-28 18:39, Yuri Voinov wrote: >> It seems bug. > > > On 2016-10-28 19:53, Alex Rousskov wrote: >>> Is it a bug, documentation error or I simply missed something? >> >> It is a bug IMO. The documented intent sounds worth supporting to

Re: [squid-users] Default state for the option generate-host-certificates

2016-10-28 Thread Garri Djavadyan
On 2016-10-28 18:39, Yuri Voinov wrote: It seems bug. On 2016-10-28 19:53, Alex Rousskov wrote: Is it a bug, documentation error or I simply missed something? It is a bug IMO. The documented intent sounds worth supporting to me. Thanks. I've opened the report [1]. [1]

Re: [squid-users] Default state for the option generate-host-certificates

2016-10-28 Thread Alex Rousskov
On 10/28/2016 06:56 AM, Garri Djavadyan wrote: > The last sentence for generate-host-certificates[=] option > paragraph states: > > This option is enabled by default when ssl-bump is used. I see no [trunk] code to match that statement. > Is it a bug, documentation error or I simply

Re: [squid-users] Default state for the option generate-host-certificates

2016-10-28 Thread Yuri Voinov
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 It seems bug. Just always specify option explicity. 28.10.2016 18:56, Garri Djavadyan пишет: > Hello list, > > The last sentence for generate-host-certificates[=] option > paragraph states: > > This option is enabled by default when

[squid-users] Default state for the option generate-host-certificates

2016-10-28 Thread Garri Djavadyan
Hello list, The last sentence for generate-host-certificates[=] option paragraph states:   This option is enabled by default when ssl-bump is used. See the   ssl-bump option above for more information. But a client can't negotiate secure connection and times out when the option is not