From 51467ded12c5fe52757bd491404423859c18c27f Mon Sep 17 00:00:00 2001 From: Thomas Camlong Date: Sat, 8 Aug 2026 09:09:53 +0200 Subject: [PATCH] docs: remove obsolete X-Frame-Options ALLOW-FROM examples ALLOW-FROM is not supported by any modern browser. The CSP frame-ancestors directive is the correct replacement and was already present in both examples. --- apps/docs/docs/widgets/iframe/index.mdx | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/apps/docs/docs/widgets/iframe/index.mdx b/apps/docs/docs/widgets/iframe/index.mdx index 5be26f3b2..cfa3a9e69 100644 --- a/apps/docs/docs/widgets/iframe/index.mdx +++ b/apps/docs/docs/widgets/iframe/index.mdx @@ -45,20 +45,18 @@ Some proxies disallow iframes by default for this reason. You can use https://iframetest.com to check, if the site is allowing iframes. If you manage all of your own applications, you can usually change that by configuring -the appropriate headers (such as `X-Frame-Options` or `Content-Security-Policy`) to allow iframes. +the appropriate headers (such as `Content-Security-Policy`) to allow iframes. For example, to allow your site to be embedded in iframes from specific domains: **Apache (.htaccess or httpd.conf):** ```apache Header set Content-Security-Policy "frame-ancestors 'self' https://trusted-domain.com" -Header set X-Frame-Options "ALLOW-FROM https://trusted-domain.com" ``` **Nginx:** ```nginx add_header Content-Security-Policy "frame-ancestors 'self' https://trusted-domain.com"; -add_header X-Frame-Options "ALLOW-FROM https://trusted-domain.com"; ``` ### Example URLs