W
whenshaw
Guest
Hi Meyrick, As Manooj said, this looks like a "mixed content" problem, accessing a resource over HTTP from a resource loaded via HTTPS. For development purposes, you can tell browsers to allow the mixed content (they'll still give you a warning, but will load the HTTP resource). Information about how Chrome handles this, with workarounds, is here: https://support.google.com/chrome/answer/1342714 Are you using Chrome, and if so, what version are you using? When was the last time that your application ran correctly? Regards, --Wayne From: Manooj Murali [mailto:bounce-mmurali@community.progress.com] Sent: Monday, October 13, 2014 3:29 AM To: TU.Mobile@community.progress.com Subject: RE: [Technical Users - Mobile] blocked RE: blocked Reply by Manooj Murali ok.. so this looks like a standard error that comes up when you are accessing non-https content from a https. Please have a look at this stack post : stackoverflow.com/.../blocked-the-page-at-x-was-loaded-over-https-but-ran-insecure-content-from . May be you should check where and who is accessing the http link and correct it to https. Stop receiving emails on this subject. Flag this post as spam/abuse.
Continue reading...
Continue reading...