this may be a dumb ssl question, but here goes...

[Aaron]

I noticed that, but it appears to require a page / uri. I think the special 444 should not return content, if I am reading its design correctly. 

-Aaron 

Maxim Dounin <mdounin at mdounin.ru> wrote:

>Hello!
>
>On Thu, Oct 11, 2012 at 11:35:16AM -0400, AJ Weber wrote:
>
>> I didn't double-check yet, but it looks like if I set this up, and
>> the client does not have a client-side certificate, nginx is
>> returning either a 400 (or more likely a 403)?  Is there any way I
>> can be entirely "rude" and re-map the return code if you do not have
>> a client certificate to 444?
>
>The answer is on the very same page:
>http://nginx.org/en/docs/http/ngx_http_ssl_module.html#errors
>
>-- 
>Maxim Dounin
>http://nginx.com/support.html
>
>_______________________________________________
>nginx mailing list
>nginx at nginx.org
>http://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20121011/e5cb5e1f/attachment.html>