But I'm not actually seeing an answer as to what can be done. X-frame-options seem to be something that is set on the server. And if that is the case then it seems that there isn't anything I can do. But then I'm confused why the webb object shows up in IE, but not Chrome. Both browsers support x-frame-options headers.
Chrome Version 37.0.2062.120 m and IE 9.0.8112.16421. Yes it is in the intended environment (our LMS) and published for the LMS. Everything else is working correctly.
Our LMS is using the https protocol, so I don't think it is that.
So that leaves x-frame-options headers. But if it is that, why is it that it works in IE and doesn't in Chrome? Both of those browsers support x-frame-options. And if it is that, what can be done about it? What request would I need to make to my LMS team regarding changes to their server to get that fixed -- if it is even possible. Is there a way for me to determine what settings are on our LMS server?
From my research it seems that maybe our LMS server has x-frame-options set to Allow-From which isn't properly supported in Chrome? I found this bug issue https://bugs.webkit.org/show_bug.cgi?id=94836 and it seems that means it isn't going to be fixed any time soon.
If I understand it correctly it means that if a server hasn't implemented x-frame-options then pages from that server will be iframeable. And if it has implement Deny or Same-Domain then any browser which supports x-frame-options will respect that too. But if the server has implemented Allow-From then IE, FireFox, etc. will repsect that, but Chrome will treat it as a Deny.
This seems like a big problem for using webobjects in Storyline. Is there anything all y'all can do to push the Chrome folks to get Allow-From to work properly?
It sounds like you're on the right track with that bug - and I wish there was something we could do to push Chrome along...but we're typically in the same boat as you in terms of filing bugs. To help you narrow down the issue, you may want to also test your course in a few environments outside your LMS - such as SCORM Cloud (it's a free, industry standard testing method for SCORM content) and any of the web servers mentioned in this article. Have you tested it in new versions of IE as well?
3 Replies
Hi R,
What version of Chrome and IE are you using? Did you look further into the two solutions at the bottom of that article?
You'll also want to confirm that you're testing the published output within the intended environment, as testing it locally may be a part of the problem you're running into.
Chrome Version 37.0.2062.120 m and IE 9.0.8112.16421. Yes it is in the intended environment (our LMS) and published for the LMS. Everything else is working correctly.
Our LMS is using the https protocol, so I don't think it is that.
So that leaves x-frame-options headers. But if it is that, why is it that it works in IE and doesn't in Chrome? Both of those browsers support x-frame-options. And if it is that, what can be done about it? What request would I need to make to my LMS team regarding changes to their server to get that fixed -- if it is even possible. Is there a way for me to determine what settings are on our LMS server?
From my research it seems that maybe our LMS server has x-frame-options set to Allow-From which isn't properly supported in Chrome? I found this bug issue https://bugs.webkit.org/show_bug.cgi?id=94836 and it seems that means it isn't going to be fixed any time soon.
If I understand it correctly it means that if a server hasn't implemented x-frame-options then pages from that server will be iframeable. And if it has implement Deny or Same-Domain then any browser which supports x-frame-options will respect that too. But if the server has implemented Allow-From then IE, FireFox, etc. will repsect that, but Chrome will treat it as a Deny.
This seems like a big problem for using webobjects in Storyline. Is there anything all y'all can do to push the Chrome folks to get Allow-From to work properly?
Hi R,
It sounds like you're on the right track with that bug - and I wish there was something we could do to push Chrome along...but we're typically in the same boat as you in terms of filing bugs. To help you narrow down the issue, you may want to also test your course in a few environments outside your LMS - such as SCORM Cloud (it's a free, industry standard testing method for SCORM content) and any of the web servers mentioned in this article. Have you tested it in new versions of IE as well?
This discussion is closed. You can start a new discussion or contact Articulate Support.