(originally reported by mattamattam)
We're using the beta files served up by the msft CDN. In start.js, there's some code to sniff whether to load the http or https version of the pages from the cdn for jquery. Problem is this code has a bug in the compare function and always returns the http version of jquery script, so we get the alert message appearing about loading non-secure content on a secure page. This is a particularly nasty bug. We've had to diverge start.js locally which means we essentialy lose the use of the cdn. The offending line is in start.debug.js line 1045:
var ajaxPath = (window.location.protocol === "https" ? "https" : "http") + "://ajax.microsoft.com/ajax/";
it should be
var ajaxPath = (window.location.protocol === "https:" ? "https" : "http") + "://ajax.microsoft.com/ajax/";
the window.location.protocol includes the colon (:) in the string, so the string compare always fails for https.
Please fix so we can go back to using the CDN...:)
We're using the beta files served up by the msft CDN. In start.js, there's some code to sniff whether to load the http or https version of the pages from the cdn for jquery. Problem is this code has a bug in the compare function and always returns the http version of jquery script, so we get the alert message appearing about loading non-secure content on a secure page. This is a particularly nasty bug. We've had to diverge start.js locally which means we essentialy lose the use of the cdn. The offending line is in start.debug.js line 1045:
var ajaxPath = (window.location.protocol === "https" ? "https" : "http") + "://ajax.microsoft.com/ajax/";
it should be
var ajaxPath = (window.location.protocol === "https:" ? "https" : "http") + "://ajax.microsoft.com/ajax/";
the window.location.protocol includes the colon (:) in the string, so the string compare always fails for https.
Please fix so we can go back to using the CDN...:)