I'm not sure that's allowed under the Terms of Service<https://developers.google.com/chart/terms>(downloading the Visualization API to host it locally is forbidden, I don't know if that applies to the loader API or not). In any case, the loader API itself is quite small and isn't likely to present a bottleneck, ad if google changes anything on their end, you could break connectivity for your users.
On Wednesday, May 1, 2013 2:08:08 AM UTC-4, Manu Zhang wrote: > > that's it! I downloaded jsapi and included in my project in fear that > loading from www.google.com/jsapi may take too long. > > On Wednesday, May 1, 2013 1:30:44 PM UTC+8, asgallant wrote: >> >> Use a protocol-agnostic URL in the script tag: >> >> <script type="text/javascript" src="//www.google.com/jsapi" /> >> >> That should make it load from https when the user is accessing from a >> secure site, which should clear up the security issue. >> >> On Wednesday, May 1, 2013 1:16:41 AM UTC-4, Manu Zhang wrote: >>> >>> I have a web application on GAE which loads corechart package. >>> But when I access the page from Chrome, my chart is not shown and I find >>> the following through "inspect element" >>> [blocked] The page at http://appid.appspot.com ran insecure content >>> from >>> http://www.google.com/uds/?file=visualization&v=1&packages=corechart. >>> >>> I don't have this issue in Firefox. It seems that Chrome blocks what it >>> considers insecure content. How to make Chrome believe it is a secure >>> source? >>> Any work around? >>> >> -- You received this message because you are subscribed to the Google Groups "Google Visualization API" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-visualization-api+unsubscr...@googlegroups.com. To post to this group, send email to google-visualization-api@googlegroups.com. Visit this group at http://groups.google.com/group/google-visualization-api?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
