Index: chrome/common/extensions/docs/templates/articles/contentSecurityPolicy.html |
diff --git a/chrome/common/extensions/docs/templates/articles/contentSecurityPolicy.html b/chrome/common/extensions/docs/templates/articles/contentSecurityPolicy.html |
index daf3f7170f4d323a8cb6258c46dda1ca05f5d48d..aec0c2b2755836ac1f5921ef6559b9519b6fc352 100644 |
--- a/chrome/common/extensions/docs/templates/articles/contentSecurityPolicy.html |
+++ b/chrome/common/extensions/docs/templates/articles/contentSecurityPolicy.html |
@@ -287,8 +287,8 @@ function main() { |
<p> |
Currently, we allow whitelisting origins with the following schemes: |
- <code>blob</code>, <code>filesystem</code>, <code>https</code>, |
- <code>chrome-extension</code>, and <code>chrome-extension-resource</code>. |
+ <code>blob</code>, <code>filesystem</code>, <code>https</code>, and |
+ <code>chrome-extension</code>. |
The host part of the origin must explicitly be specified for the |
<code>https</code> and <code>chrome-extension</code> schemes. |
Generic wildcards such as <code>https:</code>, <code>https://*</code> and |