chrome/common/extensions/docs/server2/templates/articles/contentSecurityPolicy.html - Issue 10837255: Clarifying the CSP restrictions with regard to `connect-src` and `unsafe-eval`.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: chrome/common/extensions/docs/server2/templates/articles/contentSecurityPolicy.html

Issue 10837255: Clarifying the CSP restrictions with regard to `connect-src` and `unsafe-eval`. (Closed) Base URL: svn://svn.chromium.org/chrome/trunk/src

Patch Set: Created 8 years, 4 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View side-by-side diff with in-line comments

Download patch

« no previous file with comments | « chrome/common/extensions/docs/extensions/contentSecurityPolicy.html ('k') | chrome/common/extensions/docs/static/contentSecurityPolicy.html » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Hide Comments ('s')

Index: chrome/common/extensions/docs/server2/templates/articles/contentSecurityPolicy.html

diff --git a/chrome/common/extensions/docs/server2/templates/articles/contentSecurityPolicy.html b/chrome/common/extensions/docs/server2/templates/articles/contentSecurityPolicy.html

index 2ed5b0c8c4ad266c7cb856e512c3589357f6fc0d..efd7c714507021eb798dfb74f8f1124ccfa0afa4 100644

--- a/chrome/common/extensions/docs/server2/templates/articles/contentSecurityPolicy.html

+++ b/chrome/common/extensions/docs/server2/templates/articles/contentSecurityPolicy.html

@@ -39,7 +39,9 @@

For full details regarding CSP's syntax, please take a look at

the Content Security Policy specification

- </a>.

+ </a>, and the <a href="http://www.html5rocks.com/en/tutorials/security/content-security-policy/">

+ "An Introduction to Content Security Policy"

+ </a> article on HTML5Rocks.

</p>

<h2>Default Policy Restrictions</h2>

@@ -219,7 +221,10 @@ popup.html:

<p>

There is no mechanism for relaxing the restriction against executing inline

JavaScript. In particular, setting a script policy that includes

- <code>unsafe-inline</code> will have no effect. This is intentional.

+ <code>unsafe-inline</code> will have no effect. Likewise, there is no

+ mechanism for enabling <code>eval</code>-like constructs. Setting a script

+ policy that includes <code>unsafe-eval</code> will have no effect. This is

+ intentional.

</p>

<p>

@@ -243,6 +248,14 @@ popup.html:

<code>http://localhost</code>.

</p>

+<p class="note">

+ The restriction against resources loaded over HTTP applies only to those

+ resources which are directly executed. You're still free, for example, to

+ make XMLHTTPRequest connections to any origin you like; the default policy

+ doesn't restrict <code>connect-src</code> or any of the other CSP directives

+ in any way.

+</p>

<p>

A relaxed policy definition which allows script resources to be loaded from

<code>example.com</code> over HTTPS might look like: