oyvindkinsey/easyXDM

Different Protocols http:// https://

ingozoell opened this issue · 2 comments

ingozoell commented

Hi,

I use easyXDM to dyn. resize iframe (+intermediary frame) from a different domain. Works pretty good for me.

The content of the remote iframe is a webshop that will show on my domain like http://myDomain.com – Shop-Domain looks like (different protocols by process steps)

  1. http://shop.com,
  2. http://shop.com/register,
  3. **https://**shop.com/buy // switch to https://

contained iframe

new easyXDM.Socket({
container:      "shop",
remote:         http://shop.com,

onMessage: function(message, origin){
this.container.getElementsByTagName("iframe")[0].style.height = message + "px";
}
});

document to embed

window.onload = function(){
parent.socket.postMessage(document.body.clientHeight || document.body.offsetHeight || document.body.scrollHeight);
 };

The Shop use https, too, so I get this message.

Message

Blocked a frame with origin "https://www.shop.com" from accessing a frame with origin "http://shop.com". The frame requesting access has a protocol of "https", the frame being accessed has a protocol of "http". Protocols must match.

Is it possible to add:
http://shop.com and
https://shop.com to remote?

Thanks
Ingo

oyvindkinsey commented

This is simply a warning in Chrome, and unless it's actually causing
negative side effects, is something which you can safely ignore.

Øyvind Sean Kinsey
San Francisco, CA

On Sat, Jun 29, 2013 at 5:20 AM, ingozoell notifications@github.com wrote:

Hi,

I use easyXDM to dyn. resize iframe (+intermediary frame) from a different
domain. Works pretty good for me.

The content of the remote iframe is a webshop that will show on my domain
like http://myDomain.com – Shop-Domain looks like (different protocols by
process steps)

  1. http://shop.com,
  2. http://shop.com/register,
  3. _https://_shop.com/buy // switch to https://

contained iframe

new easyXDM.Socket({
container: "shop",
remote: http://shop.com,

onMessage: function(message, origin){
this.container.getElementsByTagName("iframe")[0].style.height = message + "px";
}
});

document to embed

window.onload = function(){
parent.socket.postMessage(document.body.clientHeight || document.body.offsetHeight || document.body.scrollHeight);
};

The Shop use https, too, so I get this message.

Message

Blocked a frame with origin "https://www.shop.com" from accessing a frame
with origin "http://shop.com". The frame requesting access has a protocol
of "https", the frame being accessed has a protocol of "http". Protocols
must match.

Is it possible to add:
http://shop.com and
https://shop.com to remote?

Thanks

Ingo

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/231
.

ingozoell commented

Thanks.
I could turn the protocol to https:// absolutely. No more warnings.