3 ms·
Many websites like Google, Twitter or GitHub, refuse to show content in cross domain iframe, for secure reason. It is the browser that refuses to show the cont
by brudgers 10y ago
Many websites like Google, Twitter or GitHub, refuse to show content in cross domain iframe, for secure reason.
It is the browser that refuses to show the content. The behavior is in response to an HTTP header. See: http://stackoverflow.com/a/19843216 http://stackoverflow.com/a/19843216
If X-Frame-Options is removed from the HTTP stream, the modified page can be displayed. Browser scripting or a 'Man in the middle' attack (on the content provider not the user) are possible approaches to working around the limitation.
- pd4d10 10y agoThanks for your clarification. I've updated README to clarify this. https://github.com/pd4d10/chrome-ui/blob/master/README.md https://github.com/pd4d10/chrome-ui/blob/master/README.md
- brudgers 10y agoI pointed it out for the sake of suggesting a work around. I'm a big fan of people taking control of their own browsers and I dislike that X_FRAME-OPTIONS is designed to prevent people from mashing up web content however they want.