Getting an ActiveX warning when I load a page via HTTP that has an HTTPS remote javascript included

So basically I have a basic page that is loaded via http.

Inside this application I want to include a remotely hosted JS file. Currently when I load the page I always have the active X warning about security. I pretty much tried every possible way to include th Javascript file (jquery.getScript, creating a node programmatically, escaping characters and all that stuff).

The JS file itself is on a domain that is on HTTPS but that the certificate is not valid (pointing somewhere else apparently). (It's our QA server). I do not have access on the server and therefore am not able to modify anything ser开发者_如何学Gover side.

If I click on the warning and select "Display blocked content" the JS file is still not loaded.

The warning bar itself says :

To help protect your security, Internet Explorer has blocked this website from displaying content with security certificate error. Click here for options...

Options are :

• Display blocked content
• What's the risk ?
• Information bar help

If I go to the javascript file itself I have this warning :

There is a problem with this website's security certificate.

 The security certificate presented by this website was issued for

a different website's address.

Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server. We recommend that you close this webpage and do not continue to this website. Click here to close this webpage. Continue to this website (not recommended).

Is there a way to make a workaround ?

This message: "The security certificate presented by this website was issued for a different website's address" means that the URL/hostname that you're using to access the site isn't the URL/hostname for which the site has a certificate. If you run Fiddler (www.fiddler2.com) with HTTPS-decryption enabled, you'll get a popup alert that explains this mismatch more clearly (specifically, by showing you what Hostname the server is expecting you to be using). You can then correct your markup to refer to the site using the correct hostname, which will correct the certificate error and make the problem go away.