Re: https redirect needed
Thank you! On Tue, Jul 17, 2018, 2:18 AM Shazron wrote: > Thanks! > https://issues.apache.org/jira/browse/CB-14210 > > > On Tue, Jul 17, 2018 at 2:21 AM wrote: > > > > Depending on how the site is deployed, you might need > > https://stackoverflow.com/a/37006232/380229 > > > > Full disclosure: that's an answer by me. > > > > Shazron schrieb am Mo., 16. Juli 2018, 07:50: > > > > > How: > > > https://stackoverflow.com/a/13376283 > > > > > > Where: > > > https://svn.apache.org/repos/asf/cordova/site/public/.htaccess > > > > > > > > > On Mon, Jul 16, 2018 at 11:21 AM Shazron wrote: > > > > > > > > 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 > > > 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: dev-unsubscr...@cordova.apache.org > > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > > > > - > > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: https redirect needed
Thanks! https://issues.apache.org/jira/browse/CB-14210 On Tue, Jul 17, 2018 at 2:21 AM wrote: > > Depending on how the site is deployed, you might need > https://stackoverflow.com/a/37006232/380229 > > Full disclosure: that's an answer by me. > > Shazron schrieb am Mo., 16. Juli 2018, 07:50: > > > How: > > https://stackoverflow.com/a/13376283 > > > > Where: > > https://svn.apache.org/repos/asf/cordova/site/public/.htaccess > > > > > > On Mon, Jul 16, 2018 at 11:21 AM Shazron wrote: > > > > > > 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 > > 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: dev-unsubscr...@cordova.apache.org > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: https redirect needed
Depending on how the site is deployed, you might need https://stackoverflow.com/a/37006232/380229 Full disclosure: that's an answer by me. Shazron schrieb am Mo., 16. Juli 2018, 07:50: > How: > https://stackoverflow.com/a/13376283 > > Where: > https://svn.apache.org/repos/asf/cordova/site/public/.htaccess > > > On Mon, Jul 16, 2018 at 11:21 AM Shazron wrote: > > > > 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 > 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: dev-unsubscr...@cordova.apache.org > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: https redirect needed
This is because I haven't done the .htaccess changes yet On Mon, Jul 16, 2018 at 7:42 PM Chris Brody wrote: > http://cordova.apache.org/ still does not seem to be redirected; the > others look good > > Wondering if they should do something in the Apache org itself for the > other project pages? > On Mon, Jul 16, 2018 at 1:50 AM Shazron wrote: > > > > How: > > https://stackoverflow.com/a/13376283 > > > > Where: > > https://svn.apache.org/repos/asf/cordova/site/public/.htaccess > > > > > > On Mon, Jul 16, 2018 at 11:21 AM Shazron wrote: > > > > > > 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 > 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: dev-unsubscr...@cordova.apache.org > > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > >
Re: https redirect needed
http://cordova.apache.org/ still does not seem to be redirected; the others look good Wondering if they should do something in the Apache org itself for the other project pages? On Mon, Jul 16, 2018 at 1:50 AM Shazron wrote: > > How: > https://stackoverflow.com/a/13376283 > > Where: > https://svn.apache.org/repos/asf/cordova/site/public/.htaccess > > > On Mon, Jul 16, 2018 at 11:21 AM Shazron wrote: > > > > 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 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: dev-unsubscr...@cordova.apache.org > > > For additional commands, e-mail: dev-h...@cordova.apache.org > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: https redirect needed
How: https://stackoverflow.com/a/13376283 Where: https://svn.apache.org/repos/asf/cordova/site/public/.htaccess On Mon, Jul 16, 2018 at 11:21 AM Shazron wrote: > > 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 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: dev-unsubscr...@cordova.apache.org > > For additional commands, e-mail: dev-h...@cordova.apache.org > > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
Re: https redirect needed
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 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: dev-unsubscr...@cordova.apache.org > For additional commands, e-mail: dev-h...@cordova.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@cordova.apache.org For additional commands, e-mail: dev-h...@cordova.apache.org
