[Building Sakai] Web Content and X-Frame-Options

[Sam Ottenhoff]

It looks like more and more top sites are starting to use the HTTP
header X-Frame-Options set to SAMEORIGIN.

The effect on Sakai is that our Web Content tool iframes external content
and this header will prevent the content from loading.  Try adding a Web
Content tool from www.google.com, www.youtube.com, or twitter.com.  In a
recent browser like Firefox 8, the iframe will not render.

What are the preferred solutions?

1) Change Web Content into a proxy instead of a pure iframe?

2) Detect this header and tell the user it's impossible?

3) New option in Web Content to grant a full window to a Web Content tool
instead of an iframe?

--Sam
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20111229/2b3f93c7/attachment.html