ansaurus

Question

Iframe permission denied error when developing locally: what are my options?

Answer 1

+2 A:

You can use fragment id messaging, which is a hack that uses window.location.hash (the part of the URL following #) to communicate. This test page has an example. There are also libraries such as Dojo that facilitate this.

If you only need to support recent browsers, you can use postMessage.

Matthew Flaschen 2010-06-04 12:22:58

Thanks for the answer! Could you elaborate a bit on what this is or how to accomplish that?

marcgg 2010-06-04 12:24:13

Here is the idea - Code in one window/iframe can write (but not read) the location of every other iframe on the page, even it belongs to another domain. So, iframe A will modify the url of iframe B by adding some content after the # (fragment identifier). Iframe B on the other hand will continuously monitor its url to identify the message. I believe there are libraries that insulate you from the gory details, you would just have to google it up.

sri 2010-06-04 12:35:34

If this is to be applied then you should go for a ready cooked solution like easyXDM. Its far beyond what Dojo (and any other library) has. But I would personally go with the proxy in this case, its not difficult and could be provided via a simple script.

Sean Kinsey 2010-06-04 13:58:34

Answer 2

+2 A:

In addition to the postMessage and location hash that Matthew mentions above, you may want to consider using a proxy server running locally. The proxy server will listen on port 80 and forward to the appropriate target port based on the domain name specified in the http request. Then you just access your website normally on port 80 and things should work properly.

sri 2010-06-04 12:41:29

The proxy idea is good but it would require everyone on the team to set up this proxy and this wouldn't be acceptable...

marcgg 2010-06-04 12:48:46

ansaurus

tags:

views:

answers:

Iframe permission denied error when developing locally: what are my options?

related questions