I've made the redirect changes for the naked domain, as well as www subdomain.
Redirecting http://c.a.o to https://c.a.o - we will have to configure .htaccess ourselves (there will be no foundation-wide redirects https://issues.apache.org/jira/browse/INFRA-15493?jql=text%20~%20%22http%20redirect%22) Regarding https://cordova.io I'm not sure how to do this since it's just a 302 Redirect on the DNS level. On Thu, Jul 12, 2018 at 9:33 PM Chris Brody <[email protected]> wrote: > > If I navigate to http://cordova.io/, www.cordova.io, or > http://cordova.apache.org/ on Chrome (Chromium) here is what happend: > * it goes to http://cordova.apache.org/. > * I see an "i" circle in the address bar > * if I click it, it tells me that my connection is not secure > > It has already been announced that Chrome will mark sites like this as > "not secure" starting very soon. > > But navigating to https://cordova.apache.org/ works as expected. > > I think the right solution is to simply redirect http://cordova.io/, > www.cordova.io, and http://cordova.apache.org/ to the https site. > > An additional point is that if I would try navigating to > https://cordova.io I I get a message that the certificate is not > valid. Should be easy to fix with help from letsencrypt.org:) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
