<html><head/><body><html><head></head><body>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. <br>
<br>
-Aaron <br><br><div class="gmail_quote">Maxim Dounin <mdounin@mdounin.ru> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre style="white-space: pre-wrap; word-wrap:break-word; font-family: sans-serif; margin-top: 0px">Hello!<br /><br />On Thu, Oct 11, 2012 at 11:35:16AM -0400, AJ Weber wrote:<br /><br /><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">I didn't double-check yet, but it looks like if I set this up, and<br />the client does not have a client-side certificate, nginx is<br />returning either a 400 (or more likely a 403)? Is there any way I<br />can be entirely "rude" and re-map the return code if you do not have<br />a client certificate to 444?</blockquote><br />The answer is on the very same page:<br /><a href="http://nginx.org/en/docs/http/ngx_http_ssl_module.html#errors">http://nginx.org/en/docs/http/ngx_http_ssl_module.html#errors</a><br /></pre></blockquote></div></body></html></body></html>