3 ms·
If you’re providing a service like Rollbar, Bugsnag, Optimizely, etc which are scripts embedded on customer pages, with XHR api requests, it is sometimes necess
by cj 6y ago
If you’re providing a service like Rollbar, Bugsnag, Optimizely, etc which are scripts embedded on customer pages, with XHR api requests, it is sometimes necessary for the client to connect via http if you need to support certain IE versions.
For example; there are certain versions of IE that will throw an insecure content warning if you load https scripts within a http page.
And of course, many older clients don’t (and never will) support newer versions of TLS.
- jermier 6y ago> For example; there are certain versions of IE that will throw an insecure content warning if you load https scripts within a http page. Does IE support 'schemeless URIs'? like: //example.com/resource.js
- ancarda 6y ago>warning if you load https scripts within a http page Why? I get https->http, but why would an upgrade cause a warning?