Skip to content

Commit 178c4c0

Browse files
committed
docs: remove whitelist
1 parent fd2fd4d commit 178c4c0

File tree

1 file changed

+7
-5
lines changed
  • user_guide_src/source/outgoing

1 file changed

+7
-5
lines changed

user_guide_src/source/outgoing/csp.rst

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,13 @@ Content Security Policy
1212
What is Content Security Policy?
1313
********************************
1414

15-
One of the best protections you have against XSS attacks is to implement a Content Security Policy (CSP) on the site.
16-
This forces you to whitelist every single source of content that is pulled in from your site's HTML,
17-
including images, stylesheets, javascript files, etc. The browser will refuse content from sources that don't meet
18-
the whitelist. This whitelist is created within the response's ``Content-Security-Policy`` header and has many
19-
different ways it can be configured.
15+
One of the best protections you have against XSS attacks is to implement a Content
16+
Security Policy (CSP) on the site. This requires you to specify and authorize each
17+
source of content that is included in your site's HTML, including images,
18+
stylesheets, JavaScript files, and so on. The browser will reject content from
19+
sources that are not explicitly approved. This authorization is defined within
20+
the response's ``Content-Security-Policy`` header and offers various configuration
21+
options.
2022

2123
This sounds complex, and on some sites, can definitely be challenging. For many simple sites, though, where all content
2224
is served by the same domain (http://example.com), it is very simple to integrate.

0 commit comments

Comments
 (0)