No, I did not. This issue has nothing to do with same origin policy (which most users should never try to disable). It's about mixed content. Accessing a site via https can give a false sense of security if the site itself depends on non-https content.
In the past, many browsers would just show a mixed-content warning, which most users would probably ignore. Chrome's latest behavior (and I expect other browsers will follow eventually) tries to give a better indicator of the degree of security a site has by not loading mixed-content by default, and when the mixed-content is loaded, the page is explicitly marked "Not Secure". The end result is that project websites may not be presented to their users in the way the developers intended. On Fri, Jan 13, 2017 at 12:54 PM Martin Gainty <mgai...@hotmail.com> wrote: > Hi Christopher > > > did you try disabling default x-domain block for XHR request originating > from Chrome? > > > https://joshuamcginnis.com/2011/02/28/how-to-disable-same-origin-policy-in-chrome/ > > > How to: Disable Same-Origin Policy in Chrome | Josh McGinnis< > https://joshuamcginnis.com/2011/02/28/how-to-disable-same-origin-policy-in-chrome/ > > > joshuamcginnis.com > How to enable cross-domain ajax requests in Chrome for development by > disabling the same-origin policy. > > > ? > > Martin > ______________________________________________ > > > > ________________________________ > From: Christopher <ctubb...@apache.org> > Sent: Friday, January 13, 2017 12:34 PM > To: general@incubator.apache.org > Subject: HTTPS project sites > > Hi incubating projects, > > I noticed today that at least one incubating web site won't load properly > in the latest version of Chrome with the default settings using HTTPS ( > https://htrace.incubator.apache.org/). > Apache HTrace - About<https://htrace.incubator.apache.org/> > htrace.incubator.apache.org > Apache HTrace is an Apache Incubator project providing an open source > framework for distributed tracing. It can be used with both standalone > applications and libraries. > > > > > This appears to be caused by Chrome being a bit aggressive about not > loading scripts from HTTP sources when the page itself is loaded with > HTTPS. > > Projects may wish to check their sites to ensure that their javascript/css > resources are loading correctly when using HTTPS. > > -- > Christopher > -- Christopher
