Cross domain over https not working

[supergibbs]

I am having trouble setting up cross domain Respond.js over https on IE8

• The media queries aren't parsed
• New tabs/windows are popped up with the following url, one per css file. (host names changed to origin/remote):

https://origin/%20-%20#https://remote/Content/respond-proxy.html?url=https%3A%2F%2Forgin%2FContent%2Fimages%2Frespond.proxy.gif&css=https%3A%2F%2Fremote%2Fcontent%2Fcss

• IE shows in the console: SEC7111: HTTPS security is compromised by res://ieframe.dll/forbidframing.htm SEC7111: HTTPS security is compromised by res://ieframe.dll/ErrorPageTemplate.css SEC7111: HTTPS security is compromised by res://ieframe.dll/errorPageStrings.js SEC7111: HTTPS security is compromised by res://ieframe.dll/httpErrorPagesScripts.js SEC7111: HTTPS security is compromised by res://ieframe.dll/red_x.png SEC7111: HTTPS security is compromised by res://ieframe.dll/bullet.png

The exact same markup worked in our QA environment but that doesn't use https.

[supergibbs]

I've setup the cross-domain example in our staging environment and it works fine when it references githubraw.com. If I reference our domain it fails with the above symptoms.

https://hub.staging2.algdev.net/Content/example.html references https://webui.staging2.algdev.net/Content/test.css https://webui.staging2.algdev.net/Content/test2.css https://webui.staging2.algdev.net/content/respond-proxy.html

[DeweyOx]

Same issue for me....:(

[semanio]

Was anyone able to figure this out?

[scottjehl]

I’d recommend using a local server proxy for fetching the css for IE, if you really need this. Other approaches are just really hacky, unfortunately.

On Sep 16, 2014, at 10:41 AM, Nate Hanna [email protected] wrote:

Was anyone able to figure this out?

— Reply to this email directly or view it on GitHub.

[semanio]

@scottjehl so basically employ the CDN/X-Domain Setup section of the READ.ME?