Issue 415 in gwt-google-apis: support HTTPS in visualization API

10 views
Skip to first unread message

gwt-goo...@googlecode.com

unread,
Sep 15, 2010, 9:36:50 AM9/15/10
to galgwt-issue-...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 415 by phraktle: support HTTPS in visualization API
http://code.google.com/p/gwt-google-apis/issues/detail?id=415


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


gwt-goo...@googlecode.com

unread,
Sep 15, 2010, 2:56:58 PM9/15/10
to galgwt-issue-...@googlegroups.com

Comment #1 on issue 415 by zun...@google.com: support HTTPS in
visualization API
http://code.google.com/p/gwt-google-apis/issues/detail?id=415

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'

gwt-goo...@googlecode.com

unread,
Sep 22, 2010, 1:33:26 PM9/22/10
to galgwt-issue-...@googlegroups.com
Updates:
Status: CannotReproduce
Labels: API-Visualization

Comment #2 on issue 415 by zun...@google.com: support HTTPS in
visualization API
http://code.google.com/p/gwt-google-apis/issues/detail?id=415

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.

gwt-goo...@googlecode.com

unread,
Sep 20, 2012, 6:04:14 AM9/20/12
to galgwt-issue-...@googlegroups.com

Comment #3 on issue 415 by mathieu....@gmail.com: support HTTPS in
visualization API
http://code.google.com/p/gwt-google-apis/issues/detail?id=415

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.




gwt-goo...@googlecode.com

unread,
Jun 26, 2013, 6:19:26 PM6/26/13
to galgwt-issue-...@googlegroups.com

Comment #4 on issue 415 by mindbody...@gmail.com: support HTTPS in
visualization API
http://code.google.com/p/gwt-google-apis/issues/detail?id=415

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

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

gwt-goo...@googlecode.com

unread,
Jun 26, 2013, 6:20:28 PM6/26/13
to galgwt-issue-...@googlegroups.com

Comment #5 on issue 415 by mindbody...@gmail.com: support HTTPS in
visualization API
http://code.google.com/p/gwt-google-apis/issues/detail?id=415

IE warns of mixed content
Reply all
Reply to author
Forward
0 new messages