CSP: Implement `prefetch-src` directive. |
|
Issue descriptionAs discussed in https://github.com/w3c/webappsec-csp/issues/107, `prefetch-src` will give developers control over `<link rel="prefetch">` and `<link rel="prerender">` endpoints.
,
May 31 2018
Is there an issue with the current implementation? At our domain we got some ... > Refused to prefetch content from '...' because it violates the following Content Security Policy directive: "default-src 'none'". Note that 'prefetch-src' was not explicitly set, so 'default-src' is used as a fallback. ... errors, despite 'prefetch-src' being set by `prefetch-src 'self';`. This directive was explicitly added after seeing these errors in the first place.
,
Jun 2 2018
Just a minor update to my comment above. After reloading the site via DevTools, I recognized another notice "The Content-Security-Policy directive 'prefetch-src' is implemented behind a flag which is currently disabled." If I understood it correctly, "prefetch-src" is not yet supported by default, correct? Is there an option under `chrome://flags` to activate it, to see if everything would work fine afterwards? However, if this is as I assumed, it still confuses me to see some notice on how to fix it (by explicitly setting "prefetch-src"), even if this CSP directive is not yet supported ;)
,
Oct 1
Chrome 69 on Mac have issue with asking for prefetch-src, and ignoring header. I don't what to change default-src, but prefetch-src is ignored by default. If it is not used, imo, it shouldn't use it without a flag, so no errors should be thrown.
,
Oct 8
It is quite awkward that the 'pretech-src' directive is required, but not recognized unless flag is enabled.
,
Nov 30
Is there going to be a fix for this in the near future? Interested in using prefetching. |
|
►
Sign in to add a comment |
|
Comment 1 by bugdroid1@chromium.org
, Jan 16 2018