this may be a dumb ssl question, but here goes...
aweber at comcast.net
Thu Oct 11 22:07:44 UTC 2012
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.
Maxim Dounin <mdounin at mdounin.ru> wrote:
>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:
>nginx mailing list
>nginx at nginx.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the nginx