River Displayer doesn't work via https

[michaelkamleitner]

Hi all,
I just started to toy around with river4 today. Setup went basically smooth, but, when opening the river displayer through the Amazon S3 management tool, I got a broken view:

This is because Amazon by default opens the index.html through https (https://s3.amazonaws.com/river4-michael-kamleitner/index.html), and the displayers tries to include JS/CSS through insecure http (check the javascript console on chrome inspector or similar for details).

Should be easy to fix, once the domains fargo.io & static.newsriver.org support https (they don't, right now). In the meantime this is an issue potential newbies (like me) might fall over, so a notice in the README might be good!

[michaelkamleitner]

PS: however, everything works nice on http: http://s3.amazonaws.com/river4-michael-kamleitner/index.html :):)

[jancbeck]

I just stumbled upon this as well. Thanks for pointing it out here @michaelkamleitner. I've set Chrome to allow insecure scripts for that specific domain as descriped here: https://superuser.com/questions/487748/how-to-allow-chrome-browser-to-load-insecure-content