This is an automated email from the ASF dual-hosted git repository.
papegaaij pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/wicket.git
The following commit(s) were added to refs/heads/master by this push:
new 030cd2e WICKET-6747: fix typename after rename
030cd2e is described below
commit 030cd2e44f8f260a3da6096f2f772848d163c4d2
Author: Emond Papegaaij <[email protected]>
AuthorDate: Tue Mar 10 22:05:55 2020 +0100
WICKET-6747: fix typename after rename
---
wicket-user-guide/src/main/asciidoc/security/security_6.adoc | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/wicket-user-guide/src/main/asciidoc/security/security_6.adoc
b/wicket-user-guide/src/main/asciidoc/security/security_6.adoc
index bb85f8c..1cc9916 100644
--- a/wicket-user-guide/src/main/asciidoc/security/security_6.adoc
+++ b/wicket-user-guide/src/main/asciidoc/security/security_6.adoc
@@ -12,7 +12,7 @@ In developer mode, the CSP is extended with a reporting
directive that reports v
=== Configuring the Content Security Policy
-The Content Security Policy is managed by the _ContentSecurityPolicyEnforcer_
that can be accessed via _WebApplication.getCspSettings()_. This class
maintains two instances of _CSPHeaderConfiguration_, each of which contains the
directives for the CSP HTTP headers _Content-Security-Policy_ and
_Content-Security-Policy-Report-Only_. The first header defines the policies
that are actually enforced by the browser, whereas the second header defines a
policy for which the browser will only re [...]
+The Content Security Policy is managed by the _ContentSecurityPolicySettings_
that can be accessed via _WebApplication.getCspSettings()_. This class
maintains two instances of _CSPHeaderConfiguration_, each of which contains the
directives for the CSP HTTP headers _Content-Security-Policy_ and
_Content-Security-Policy-Report-Only_. The first header defines the policies
that are actually enforced by the browser, whereas the second header defines a
policy for which the browser will only re [...]
For applications that cannot adhere to a CSP, the CSP can be disabled with the
following call in your _Application_ class:
