support HTTPS in visualization API

[GoogleCodeExporter]

When using the GWT Visualization API in an SSL secured webapp, the browser 
complains about insecure elements. Please add support for this scenario.

Original issue reported on code.google.com by phraktle on 15 Sep 2010 at 1:29

[GoogleCodeExporter]

Can you identify which components the browser reports back as insecure?  Look 
at the resources fectched in your setup and report any that are prefixed with 
'http'

Original comment by zundel@google.com on 15 Sep 2010 at 6:50

[GoogleCodeExporter]

I just got word of another user sucessfully loading over https:// so this might 
just be a configuration issue and not a bug.  Please post to the Group if you 
want some further help.

Original comment by zundel@google.com on 22 Sep 2010 at 5:32

• Changed state: CannotReproduce
• Added labels: API-Visualization

[GoogleCodeExporter]

It works with firefox, but i reproduce with chromium and google chrome.
dev console output:

[blocked] The page at https://XXXXXXXXX/# ran insecure content from 
http://www.google.com/jsapi?callback=__gwt_AjaxLoader_onLoad.

Original comment by mathieu....@gmail.com on 20 Sep 2012 at 10:04

[GoogleCodeExporter]

it works in IE as well, Chrome still reports:
[blocked] The page at https://XXXXXXXXXXXXXX:top ran insecure content from 
http://www.google.com/jsapi?callback=__gwt_AjaxLoader_onLoad. 
802FC2828A68FF3EAA0B51CDEC3BC3E2.cache.html:14

Original comment by mindbody...@gmail.com on 26 Jun 2013 at 10:19

[GoogleCodeExporter]

IE warns of mixed content

Original comment by mindbody...@gmail.com on 26 Jun 2013 at 10:20