Missing redirect from qt.io to www.qt.io

[Revolt]

Going to https://qt.io fails, saying it can't be reached, instead of redirecting to https://www.qt.io/.

[JKSH]

@Revolt Thanks for reporting!

The non-HTTPS version (http://qt.io/) redirects as expected.

Pinging @tekojo

[tekojo]

Hi @Revolt
Yes, this is a known issue where it is impossible to have a top level domain that is hosted in a cloud do the ssl certificate opening and then forward to the www site. A cloud host does not have a fixed ip that would be needed for a subdomain redirect.

This is a problem for everyone.

[Revolt]

I didn't understand it as I don't know much about servers, but, can't there be a rewrite rule from qt.io to www.qt.io before any SSL stuff? Regardless, will it be fixed or it's not possible yet?

[tekojo]

@Revolt rewriting the address before ssl opening would make the connection point at a different item than the browser and certificate are expecting, ending in an error screen on the browser.

[hskoglund]

Perhaps if the certificate prices are coming down (for example https://letsencrypt.org/ are 0 US$) you could purchase 2 certificates, one for qt.io and for www.qt.io