Re: [PATCH 18 of 20] Upstream: multiple WWW-Authenticate headers (ticket #485)

2022-05-20 Thread Sergey Kandaurov
> On 13 May 2022, at 05:57, Maxim Dounin wrote: > > Hello! > > On Thu, May 12, 2022 at 01:03:37AM +0400, Sergey Kandaurov wrote: > >> On Thu, Apr 21, 2022 at 01:18:58AM +0300, Maxim Dounin wrote: >>> # HG changeset patch >>> # User Maxim Dounin >>> # Date 1650492341 -10800 >>> # Thu Apr

Re: ssl_verify_partial_chain

2022-05-20 Thread Vedran Vidovic
Hello,   thanks for the extensive answer.   I will try to pursue a solution similar to your suggestion: - convert intermediate CA certificate to trusted certificate - validate client certificate using trusted certificate   I still believe that addition of the new configuration option "ssl_verify_pa

Re: ssl_verify_partial_chain

2022-05-20 Thread Vedran Vidovic
Hello, thanks for the extensive answer. I will try to pursue a solution similar to your suggestion: - convert intermediate CA certificate to trusted certificate - validate client certificate using trusted certificate I still believe that addition of the new configuration option "ssl_verify_pa

Re: [PATCH 18 of 20] Upstream: multiple WWW-Authenticate headers (ticket #485)

2022-05-20 Thread Maxim Dounin
Hello! On Fri, May 20, 2022 at 05:51:19PM +0400, Sergey Kandaurov wrote: > > On 13 May 2022, at 05:57, Maxim Dounin wrote: > > > > On Thu, May 12, 2022 at 01:03:37AM +0400, Sergey Kandaurov wrote: > > > >> On Thu, Apr 21, 2022 at 01:18:58AM +0300, Maxim Dounin wrote: > >>> # HG changeset patch

Re: SSL contexts reuse across locations

2022-05-20 Thread Maxim Dounin
Hello! On Fri, May 20, 2022 at 06:52:54AM +, Pavel Pautov via nginx-devel wrote: > > -Original Message- > > From: Maxim Dounin > > Sent: Wednesday, May 18, 2022 11:32 > [..] > > > At very least, ngx_http_proxy_set_ssl() needs to be converted > > > into ngx_http_proxy_create_ssl(). >

Re: ssl_verify_partial_chain

2022-05-20 Thread Maxim Dounin
Hello! On Fri, May 20, 2022 at 04:02:08PM +0200, Vedran Vidovic wrote: > Hello, > > thanks for the extensive answer. > > I will try to pursue a solution similar to your suggestion: > - convert intermediate CA certificate to trusted certificate > - validate client certificate using trusted cer