From 7f54c8b8b4985539021142acee248376d8f6fb7b Mon Sep 17 00:00:00 2001 From: Rob Winch Date: Mon, 19 Sep 2016 10:21:04 -0500 Subject: [PATCH] Fix link to CSP in Reference Doc Previously the link in the reference from x-frame-options to the content security policy section was broken. This commit fixes the link. Issue gh-4063 --- docs/manual/src/docs/asciidoc/index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/manual/src/docs/asciidoc/index.adoc b/docs/manual/src/docs/asciidoc/index.adoc index db1cb41b4d..a8672c1ce2 100644 --- a/docs/manual/src/docs/asciidoc/index.adoc +++ b/docs/manual/src/docs/asciidoc/index.adoc @@ -4038,7 +4038,7 @@ Allowing your website to be added to a frame can be a security issue. For exampl [NOTE] ==== -Another modern approach to dealing with clickjacking is to use <>. +Another modern approach to dealing with clickjacking is to use <>. ==== There are a number ways to mitigate clickjacking attacks. For example, to protect legacy browsers from clickjacking attacks you can use https://www.owasp.org/index.php/Clickjacking_Defense_Cheat_Sheet#Best-for-now_Legacy_Browser_Frame_Breaking_Script[frame breaking code]. While not perfect, the frame breaking code is the best you can do for the legacy browsers.