The discussion revolves around an invalid X-Frame-Options header value (ALLOWALL) being set by the embed controller in Discourse, which is not a valid specification per MDN. hjr265 points out that the header is obsolete and should be removed, as the frame-ancestors directive in Content-Security-Policy has superseded it. Falco confirms the issue and notes it has been resolved in a related fix, referencing a meta-discourse post on mitigating XSS attacks with CSP 37.
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:
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.
I think so, yes. I am assuming you meant removing it from Discourse (vs. hiding it using some Nginx configuration). The header itself is considered obsolete now anyway. There are other occurrences of the same header in that file.
Note: The Content-Security-Policy HTTP header has a frame-ancestors directive which obsoletes this header for supporting browsers.