Respond icon indicating copy to clipboard operation
Respond copied to clipboard

respond proxy starts endless loop of popups when used cross-domain

Open kevinlisota opened this issue 11 years ago • 9 comments

My CSS is hosted on a CDN, so I need to use the cross-domain proxy for respond.js.

I have configured everything correctly.

  1. respond.min.js loaded locally
  2. respond-proxy.html link is on the CDN
  3. respond.proxy.gif link is local
  4. respond.proxy.js loaded locally

When running this in IE8 (Vista virtual machine using real IE8), I get an infinite loop of popup windows. The windows are opened so quickly and in such quantity that I cannot diagnose the issue. Has anyone seen this?

Specifically it looks like each new window opens this sort of URL:

http://www.mysite.com/#http://cdn.mysite.com/respond-proxy.html?url=http://www.mysite.com/respond-proxy.gif&css=http://cdn.mysite.com/something.css

Each time a URL like that is opened, it spawns another window.

Hoping someone out there has seen this behavior as it is really hard to troubleshoot. Oddly, I have a second virtual machine running WinXP and IE7 which properly loads the respond proxy css files from this very same site.

kevinlisota avatar Jan 01 '14 22:01 kevinlisota

I'm seeing the exact same behavior.

danshort avatar Jan 09 '14 19:01 danshort

Quick question, guys -- do you have a <base> tag set by chance?

goldibex avatar Jan 16 '14 00:01 goldibex

Experiencing the same issue - any ideas?

IE8 on XP virtual machine. In my case the new windows are all http://www.mysite.com/#http://www.mysite.com/respond-proxy.gif

Not not using a <base> tag.

danielparas avatar Jan 23 '14 11:01 danielparas

Related to #250

supergibbs avatar Feb 07 '14 13:02 supergibbs

Seeing the same behavior. It looks to be doing this for all of the static assets.

pierceray avatar Apr 22 '14 19:04 pierceray

I saw this issue when I incorrectly labeled the id tag on the respond.proxy.gif. Make sure your id and rel tags are correct on the assets (respond-proxy and respond-redirect).

brianlucas avatar Jun 19 '14 00:06 brianlucas

I was having the same issue but found a workaround that at least worked in my case. Turns out it was because I changed the header "X-Frame-Options" from "SAMEORIGIN" to "DENY". Setting it back to "SAMEORIGIN" fixed it right back up.

evanleck avatar Sep 08 '14 21:09 evanleck

Seeing the same problem today with version 1.4.2.

AndClarke avatar Aug 25 '15 22:08 AndClarke

Very painful. Having the same issue here. Any ideas, how this can be solved?

aufdenpunkt avatar Mar 21 '16 14:03 aufdenpunkt