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: [صورة] 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 …

ويتم تعيين ترويسة استجابة غير صالحة من وحدة تحكم التضمين

الدعم

Falco (Falco) 23 مارس 2021، 12:17ص 4

تم إصلاح هذا الآن:

الموضوع		الردود	مرات العرض
Browser prevents Discourse from rendering in iframe despite proper configuration (`X-Frame-Options: SAMEORIGIN`) Bug embedding	0	130	12 نوفمبر 2024
Embedded comments not displayed due to X-Frame-Options DENY Support	11	3397	18 يوليو 2016
Embedding error Support	13	4082	21 نوفمبر 2020
Refused to display in a frame because it set 'X-Frame-Options' to 'sameorigin' Support	6	46206	11 نوفمبر 2018
CSP Frame Ancestors enabled by default Announcements	3	1728	5 أغسطس 2021

ويتم تعيين ترويسة استجابة غير صالحة من وحدة تحكم التضمين

الموضوعات ذات الصلة