Thank you Sergey, this workaround suffices for us for now.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236546,236618#msg-236618
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Thanks for your reply. My application does not require the entire
certificate, so I am just forwarding $ssl_client_s_dn in a custom header
without any problems.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,236546,236599#msg-236599
___
nginx
On 25 Feb2013, at 18:37 , Lynoure wrote:
>> The $ssl_client_cert variable abuses header continuation, and this
>> doesn't work with many http servers (including nginx itself).
>
> Noticed that with spray-can.
>
>> There should be more portable way to pass client certificate to an
>> upstream
> The $ssl_client_cert variable abuses header continuation, and this
> doesn't work with many http servers (including nginx itself).
Noticed that with spray-can.
> There should be more portable way to pass client certificate to an
> upstream server.
Is there already, or is there one in plans? A
Hello!
On Sun, Feb 24, 2013 at 09:41:38AM -0500, jstrybis wrote:
> Hello,
>
> I am having an issue while verifying client SSL certificates. Everything
> works fine until I attempt to forward the cert onto the upstream.
>
> Once I add a line similar to the following in my location block, all
> r
Hello,
I am having an issue while verifying client SSL certificates. Everything
works fine until I attempt to forward the cert onto the upstream.
Once I add a line similar to the following in my location block, all
requests become an error 400 Bad Request.
> proxy_set_header X-SSL-Client_Cert $ss
