Hi Just changed it I see that we have an issue with http links. Website has a plugin to remove http: and https: this is to ensure chrome and the rest of browsers to show we have a safe green address bar (with the lock icon)
since there's no "exception" rule, we need to post process before publish to public site and fix this links: the links that I identified are: //apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/ <https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs/lastSuccessfulBuild/artifact/out/> //apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/ <https://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-asjs_jsonly/lastSuccessfulBuild/artifact/out/> //apache-royale-users.20374.n8.nabble.com/ <https://apache-royale-users.20374.n8.nabble.com/> //apache-royale-development.20373.n8.nabble.com/ <https://apache-royale-development.20373.n8.nabble.com/> and add to all of this "http:" I updated release manage website info here with this data: https://github.com/apache/royale-asjs/wiki/Release-Manger-(Web-Site) El jue., 30 may. 2019 a las 10:03, Piotr Zarzycki (< [email protected]>) escribió: > Yes it will resolve the problem. > > czw., 30 maj 2019 o 09:50 Carlos Rovira <[email protected]> > napisał(a): > > > So, > > > > should I change Nabble links in this page: > > > > https://royale.apache.org/mailing-lists/ > > > > like this one: > > > > https://apache-royale-users.20374.n8.nabble.com/ > > > > to > > > > http://apache-royale-users.20374.n8.nabble.com/ > > > > ? > > > > this should solve the problem? > > > > thanks > > > > > > El jue., 30 may. 2019 a las 7:47, Piotr Zarzycki (< > > [email protected]>) > > escribió: > > > > > Hi Guys, > > > > > > -1 for removing babble from the list. > > > > > > +1 For switching to http. > > > > > > Thanks, > > > Piotr > > > > > > On Thu, May 30, 2019, 6:10 AM Harbs <[email protected]> wrote: > > > > > > > More details in this link: > > > > http://support.nabble.com/HTTPS-SSL-urgent-td7594627.html#a7594635 < > > > > http://support.nabble.com/HTTPS-SSL-urgent-td7594627.html#a7594635> > > > > > > > > Simply put: Nabble does not support https. > > > > > > > > We can either keep those links as http, or get rid of Nabble… > > > > > > > > Harbs > > > > > > > > > On May 30, 2019, at 6:26 AM, Harbs <[email protected]> wrote: > > > > > > > > > > Looks like a problem with https on Nabble: > > > > > > > > > > > > > > > http://support.nabble.com/problem-with-security-certificate-with-nabble-forum-td7597896.html > > > > < > > > > > > > > > > http://support.nabble.com/problem-with-security-certificate-with-nabble-forum-td7597896.html > > > > > > > > > > > > > > >> On May 29, 2019, at 10:42 PM, QA <[email protected] > <mailto: > > > > [email protected]>> wrote: > > > > >> > > > > >> Is anyone else getting errors when viewing the mailing list from > the > > > > web page? > > > > >> > > > > >> https://royale.apache.org/mailing-lists/ < > > > > https://royale.apache.org/mailing-lists/> > > > > >> > > > > >> This server could not prove that it is* > > > > apache-royale-development.20373.n8.nabble.com*; > > > > >> > > > > > > > > > > > > > > > > > > > > > > -- > > Carlos Rovira > > http://about.me/carlosrovira > > > > > -- > > Piotr Zarzycki > > Patreon: *https://www.patreon.com/piotrzarzycki > <https://www.patreon.com/piotrzarzycki>* > -- Carlos Rovira http://about.me/carlosrovira
