On Oct 14, 1:44 pm, ZiMB LLC <[email protected]> wrote:
> So, I got all excited when I realized I could load the CDN using HTTPS
> but when I fired it up, I still got that stupid mixed content warning
> from Internet Explorer saying that some items were insecure.  Well, I
> looked into the header and it looks like dojo.require is still pulling
> the required elements from an http: based location which, to me, sorta
> defeats the whole purpose of having an https CDN.

This problem is due to a bug on how paths are resolved in Dojo. This
bug tracks the issue:
http://bugs.dojotoolkit.org/ticket/8546

However, you can work around it by modifying the modulePaths used
inside dojo.xd.js by doing the following:

<script type="text/javascript">
djConfig = {
  modulePaths: {
    "dojo": "https://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dojo";,
    "dijit": "https://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dijit";,
    "dojox": "https://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dojox";
  }
};
</script>
<script src="https://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dojo/
dojo.xd.js" type="text/javascript"></script>

James

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google AJAX APIs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/google-ajax-search-api?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to