Welcome! Log In Create A New Profile

Advanced

Re: 400 bad request with ssl_verify_client optional

Maxim Dounin
June 28, 2018 09:30AM
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 client request headers,
>
> Is there anyway to ignore the time check?

The only thing you can do if client presents an invalid certificate is
to handle this via the error_page directive, see here:

http://nginx.org/en/docs/http/ngx_http_ssl_module.html#errors

In the error_page you can even recover to normal request handling,
but I wouldn't recommend doing this, as this can easily result in
security problems if a configuration uses $ssl_client_*
variables without checking $ssl_client_verify first.

--
Maxim Dounin
http://mdounin.ru/
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

400 bad request with ssl_verify_client optional

djczaski June 27, 2018 08:28PM

Re: 400 bad request with ssl_verify_client optional

Sergey Kandaurov June 28, 2018 06:08AM

Re: 400 bad request with ssl_verify_client optional

Maxim Dounin June 28, 2018 09:30AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 170
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready