# Support embedding Discourse in an iframe **URL:** https://meta.discourse.org/t/support-embedding-discourse-in-an-iframe/50405 **Category:** Feature **Tags:** embedding **Created:** [2016年九月20日 18:46 UTC](https://meta.discourse.org/t/support-embedding-discourse-in-an-iframe/50405 "2016-09-20T18:46:09Z") **Posts on this page:** 17 **Page:** 1
### Author: ![aarongray](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aarongray/32/121516_2.png) [@aarongray](https://meta.discourse.org/u/aarongray) #### Post date: [2016年九月20日 18:46 UTC](https://meta.discourse.org/t/support-embedding-discourse-in-an-iframe/50405/1 "2016-09-20T18:46:09Z")
Howdy! I’m developing a web app, and I’d love to use Discourse as my forums / community discussion platform. One of my main requirements though is that the forum should be able to be opened in an iframe docked to the side of my UI, so that users can browse tutorials, talk to other people, or contact support all within the comfort of the app itself. This is a huge win for UX, and because Discourse is responsive and mobile friendly, a small iframe should work well for this use case. It seems like this would be an awesome feature for Discourse that many people might use. I saw this old discussion about [this topic](https://meta.discourse.org/t/discourse-not-shown-in-iframe/26970/5), which includes [one proposed solution](https://meta.discourse.org/t/discourse-not-shown-in-iframe/26970/5). So I wanted to ask the maintainers and folks here, is this a feature that you would be open to a PR for? Would you consider adding this feature? Are there any issues with that solution that was proposed that would need to be dealt with? ---
### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague) #### Post date: [2016年九月20日 19:09 UTC](https://meta.discourse.org/t/support-embedding-discourse-in-an-iframe/50405/2 "2016-09-20T19:09:31Z")
> [@aarongray](#): > > Are there any issues The main issue I see is that of opening up possible Security problems. eg. [Cross Frame Scripting](https://www.owasp.org/index.php/Cross_Frame_Scripting) ---
### Author: ![aarongray](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aarongray/32/121516_2.png) [@aarongray](https://meta.discourse.org/u/aarongray) #### Post date: [2016年九月20日 19:18 UTC](https://meta.discourse.org/t/support-embedding-discourse-in-an-iframe/50405/3 "2016-09-20T19:18:59Z")
Interesting, thanks for pointing that out. If Cross Frame Scripting was a concern, could we allow people to specify a trusted domain(s)? For example, the `ALLOW-FROM` URI in the `X-FRAME-OPTIONS` header. See [here](https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet#Defending_with_X-Frame-Options_Response_Headers). ---
### Author: ![Mittineague](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mittineague/32/114259_2.png) [@Mittineague](https://meta.discourse.org/u/Mittineague) #### Post date: [2016年九月20日 19:27 UTC](https://meta.discourse.org/t/support-embedding-discourse-in-an-iframe/50405/4 "2016-09-20T19:27:59Z")
> [@aarongray](#): > > can you edit it? ![](https://global.discourse-cdn.com/meta/original/3X/e/a/ea81a0eed36f328c0f88f877bdc03b4db47a73b0.gif) pasted the wrong URL - link fixed > [@aarongray](#): > > could we allow people to specify a trusted domain(s)? Yes, sending headers should take care of most if not all security risks. (I say most because I don’t know if some older browsers might not use the headers) ---
### Author: ![aarongray](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/aarongray/32/121516_2.png) [@aarongray](https://meta.discourse.org/u/aarongray) #### Post date: [2016年九月20日 19:29 UTC](https://meta.discourse.org/t/support-embedding-discourse-in-an-iframe/50405/5 "2016-09-20T19:29:54Z")
Okie dokie 👍 ---
### Author: ![tophee](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tophee/32/73406_2.png) [@tophee](https://meta.discourse.org/u/tophee) #### Post date: [2017年二月21日 12:20 UTC](https://meta.discourse.org/t/support-embedding-discourse-in-an-iframe/50405/6 "2017-02-21T12:20:15Z")
Not being a developer, this thread leaves me puzzled about what the conclusion is regarding embedding discourse in an IFRAME. When you say: > [@Mittineague](#): > > aarongray: > could we allow people to specify a trusted domain(s)? > > Yes, sending headers should take care of most if not all security risks. (I say most because I don’t know if some older browsers might not use the headers) This sounds to me like: problem solved, especially since - in my case - everything would not only be happening under the same domain but even on the same server. But my understaning is also that this is nevertheless [not supported](https://meta.discourse.org/t/discourse-not-shown-in-iframe/26970/5) and therefore not recommended for people like me. But why? If trusted domains can be specified? ---
### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror) #### Post date: [2017年二月21日 12:55 UTC](https://meta.discourse.org/t/support-embedding-discourse-in-an-iframe/50405/7 "2017-02-21T12:55:54Z")
Because it’s an extremely fragile configuration. Discourse expects to control the browser tightly as a JavaScript app. This is not a static 1996 era web page to be slapped in an `