• Ianis G. Vasilev (15/15) Mar 31 2017 It's nice to see that all of the website's subdomains have SSL
• =?UTF-8?Q?Ali_=c3=87ehreli?= (3/17) Apr 05 2017 Ping.
• Seb (4/8) Apr 06 2017 I don't know exact details about the WordPress DLang blog, but
• Mike Parker (2/12) Apr 06 2017 I'll contact the server admin.
• Martin Nowak (3/7) Apr 09 2017 Looks like blog.dlang.org is simply missing a SNI entry (or

Ianis G. Vasilev <mail ivasilev.net> writes:

It's nice to see that all of the website's subdomains have SSL 
certificates. However, I noticed an inconsistency:

dlang.org, forum.dlang.org, code.dlang.org, tour.dlang.org, 
wiki.dlang.org all serve the same content over both http and 
https.

http://blog.dlang.org and https://blog.dlang.org, however, serve 
completely different content. The https version seems to serve 
the same page as https://digitalmars.com and, because the 
certificate is issued for digitalmars.com, browsers complain 
about it being invalid. If this is not intended behavior - maybe 
the same content should be served on both ports? Or maybe the 
subdomain should be removed in favor of https://dlang.org/blog?

Also, I don't want to start a flame war, but I think all the http 
traffic need to be redirected to https. At least for the 
subdomains that require user login.

=?UTF-8?Q?Ali_=c3=87ehreli?= <acehreli yahoo.com> writes:

Ping.

Ali

On 03/31/2017 11:33 AM, Ianis G. Vasilev wrote:
 It's nice to see that all of the website's subdomains have SSL
 certificates. However, I noticed an inconsistency:

 dlang.org, forum.dlang.org, code.dlang.org, tour.dlang.org,
 wiki.dlang.org all serve the same content over both http and https.

 http://blog.dlang.org and https://blog.dlang.org, however, serve
 completely different content. The https version seems to serve the same
 page as https://digitalmars.com and, because the certificate is issued
 for digitalmars.com, browsers complain about it being invalid. If this
 is not intended behavior - maybe the same content should be served on
 both ports? Or maybe the subdomain should be removed in favor of
 https://dlang.org/blog?

 Also, I don't want to start a flame war, but I think all the http
 traffic need to be redirected to https. At least for the subdomains that
 require user login.

Seb <seb wilzba.ch> writes:

On Wednesday, 5 April 2017 at 20:57:18 UTC, Ali Çehreli wrote:
 Ping.

 Ali

 On 03/31/2017 11:33 AM, Ianis G. Vasilev wrote:
 [...]


I don't know exact details about the WordPress DLang blog, but 
Mike does. Please ping him to follow up on this issue:
https://github.com/mdparker

Mike Parker <aldacron gmail.com> writes:

On Thursday, 6 April 2017 at 11:30:05 UTC, Seb wrote:
 On Wednesday, 5 April 2017 at 20:57:18 UTC, Ali Çehreli wrote:
 Ping.

 Ali

 On 03/31/2017 11:33 AM, Ianis G. Vasilev wrote:
 [...]


 I don't know exact details about the WordPress DLang blog, but 
 Mike does. Please ping him to follow up on this issue:
 https://github.com/mdparker

I'll contact the server admin.

Martin Nowak <code dawg.eu> writes:

On Friday, 31 March 2017 at 18:33:42 UTC, Ianis G. Vasilev wrote:
 dlang.org, forum.dlang.org, code.dlang.org, tour.dlang.org, 
 wiki.dlang.org all serve the same content over both http and 
 https.

 http://blog.dlang.org and https://blog.dlang.org

Looks like blog.dlang.org is simply missing a SNI entry (or 
support).