Bug 15378 – dlang.org does not completely work with https:

As reported on the n.g.: > The forum widget isn't going to work until the forum is also HTTPS with a valid certificate. > This week's "This Week in D" excerpt on the front page > Runnable examples on the front page (more so than usual, now they are completely broken) > Chrome warns saying that dlang connection is encrypted with obsolete cryptography

There is also a number of issues with the server-side configuration, including vulnerability to known attacks: https://www.ssllabs.com/ssltest/analyze.html?d=dlang.org&hideResults=on While perhaps not a matter of life and death in the case of dlang.org, it is certainly not good advertisement for D (cf. also the fact that it doesn't even show as "green" on Chrome).

The whole url bar showing as green is kinda rare, that signifies the extended validation thing. My bank does it but no other site I go to does.

(In reply to Adam D. Ruppe from comment #2) > The whole url bar showing as green is kinda rare, that signifies the > extended validation thing. My bank does it but no other site I go to does. I'm not talking about extended validation; just about Chrome even showing a lock symbol (which happens to be green, and also causes the https schema part of the URL to be rendered green). For example, https://www.rust-lang.org/ and https://golang.org/ show up as "secure" in this way on Chrome/OS X, while https://dlang.org does not.

That probably means mixed content. Try https://dlang.org/getstarted.html

When using the search box Firefox gives a warning that request will be sent over unencrypted channel.

https://www.ssllabs.com/ssltest/analyze.html?d=dlang.org&s=162.217.114.56&hideResults=on https://www.ssllabs.com/ssltest/analyze.html?d=dlang.org&s=2607%3afc50%3a1%3aff02%3a0%3a0%3a5%3a0&hideResults=on