On Sat, Jul 4, 2015 at 2:48 PM, Maxim Dounin <mdounin@mdounin.ru> wrote:
> Hello!
>
> On Thu, Jun 25, 2015 at 06:16:42PM +0900, Edho Arief wrote:
>
>> I noticed that trac.nginx.org has https/SNI configured for the host
>> but no actual ssl configuration (how do you even do that):
>
> The trac.nginx.org domain isn't available via https.
>
> The IP address trac.nginx.org maps to does have other sites
> answering on https/SNI though, and to avoid sending invalid
> certificate the "ssl_ciphers aNULL;" is used in the default server
> configuration. This is what causes the message you see.
>
>
>> Relevant (which is how I noticed it in the first place):
>>
>> https://github.com/EFForg/https-everywhere/pull/1993
>
> When people try to use something they weren't asked to, it
> strikes back.
>

Whoever added it probably didn't actually try accessing the
site. It has been removed. Thanks.

_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx