Re: 400 bad request with ssl_verify_client optional

2018-06-28 Thread Maxim Dounin
Hello! On Wed, Jun 27, 2018 at 08:25:38PM -0400, Danomi Czaski wrote: > I get 400 bad request when client certs are used early even though I > have ssl_verify_client optional. > > nginx: [info] 9612#0: *338 client SSL certificate verify error: > (9:certificate is not yet valid) while reading cli

Re: 400 bad request with ssl_verify_client optional

2018-06-28 Thread Sergey Kandaurov
> On 28 Jun 2018, at 03:25, Danomi Czaski wrote: > > I get 400 bad request when client certs are used early even though I > have ssl_verify_client optional. > > nginx: [info] 9612#0: *338 client SSL certificate verify error: > (9:certificate is not yet valid) while reading client request header

400 bad request with ssl_verify_client optional

2018-06-27 Thread Danomi Czaski
I get 400 bad request when client certs are used early even though I have ssl_verify_client optional. nginx: [info] 9612#0: *338 client SSL certificate verify error: (9:certificate is not yet valid) while reading client request headers, Is there anyway to ignore the time check? __