Forgive my ignorance: I'm curious about the advantage of loading the CDN files through HTTPS instead of HTTP.
On Oct 14, 4: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. > > Here are the includes I put in: > > <link href="https://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dijit/ > themes/tundra/tundra.css" rel="stylesheet" type="text/css"/> > <script src="https://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dojo/ > dojo.xd.js" type="text/javascript"></script> > > Then I require some ui elements: > > dojo.require("dijit.form.TextBox"); > dojo.require("dijit.form.ComboBox"); > dojo.require("dijit.form.CheckBox"); > > and the result in the head is this: > > <script src="http://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dijit/ > form/TextBox.xd.js" type="text/javascript"></script> > <script src="http://ajax.googleapis.com/ajax/libs/dojo/1.3.2/dijit/ > form/ComboBox.xd.js" type="text/javascript"></script> > > So, as long as this behavior continues, my users are going to have to > disable a security feature in IE (generally a hard sell) or click no > every time that warning pops up. > > Is there anyway to force this to require from the https locations? > > Thank you. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
