# En ongeldige response header wordt ingesteld vanuit de embed controller

**URL:** <https://meta.discourse.org/t/and-invalid-response-header-is-being-set-from-embed-controller/183178>\
**Category:** Product Support\
**Created:** [14 maart 2021 om 02:55 UTC](https://meta.discourse.org/t/and-invalid-response-header-is-being-set-from-embed-controller/183178 "2021-03-14T02:55:36Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![hjr265](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/hjr265/32/115215_2.png) [@hjr265](https://meta.discourse.org/u/hjr265)\
**Post date:** [14 maart 2021 om 02:55 UTC](https://meta.discourse.org/t/and-invalid-response-header-is-being-set-from-embed-controller/183178/1 "2021-03-14T02:55:37Z")

</div>

> <https://github.com/discourse/discourse/blob/53ab3dda5d5e99507096397775f3275dd63a4304/app/controllers/embed_controller.rb#L27>

MDN doesn’t specify “ALLOWALL” as a possible value for the X-Frame-Options header. On Firefox, when loading any page with an embed, this can be seen in the console:

 ![image](https://global.discourse-cdn.com/meta/original/3X/b/a/ba690b309a5bb05d6b1c98bb3548c9d817a772d7.png)

Any way to not send that header and specify the frame-ancestors directive for the Content-Security-Policy header? From the code it doesn’t seem there is a way to configure this.

---

_[View the full topic](https://meta.discourse.org/t/and-invalid-response-header-is-being-set-from-embed-controller/183178)._
