app/controllers/embed_controller.rb 53ab3dda5 @setup_url = "#{Discourse.base_url}/admin/customize/embedding" @show_reason = true @hosts = EmbeddableHost.all end render 'embed_error', status: 400 e…

I saw that error while working on the embed in our new blog . The easy thing to do is to just remove this header right?

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 …

This is fixed now: [Bild] Mitigate XSS Attacks with Content Security Policy Site Management We just landed support for CSP frame-ancestors directive. It’s disabled by default for now behind the content security policy frame ancestors site setting. You can add …

Ein ungültiger Antwortheader wird vom Embed-Controller gesetzt

Unterstützung

Falco (Falco) 23. März 2021 um 00:17 4

Das ist jetzt behoben:

Thema		Antworten	Aufrufe
Browser prevents Discourse from rendering in iframe despite proper configuration (`X-Frame-Options: SAMEORIGIN`) Bug embedding	0	129	12. November 2024
Embedded comments not displayed due to X-Frame-Options DENY Support	11	3379	18. Juli 2016
Embedding error Support	13	4044	21. November 2020
Refused to display in a frame because it set 'X-Frame-Options' to 'sameorigin' Support	6	46194	11. November 2018
CSP Frame Ancestors enabled by default Announcements	3	1717	5. August 2021

Ein ungültiger Antwortheader wird vom Embed-Controller gesetzt

Verwandte Themen