content-security-policy

Same-origin request causes “Access-Control-Allow-Origin doesn’t match” error, though origin of course matches. Note: has CSP policy w/ “sandbox”

扶醉桌前 提交于 2021-02-19 05:38:05
问题 When the exact same URL is being used in both by CORS and its web pages' URL, I still get the same error messages in my Firefox development console. Browser console messages were: Cross-Origin Request Blocked: \ The Same Origin Policy disallows reading the remote resource \ at https://egbert.net/fonts/fontawesome-webfont.woff2?v=4.7.0. \ (Reason: CORS header ‘Access-Control-Allow-Origin’ does not \ match ‘https://egbert.net’). Header Settings, lighttpd Server Access-Control-Allow-Origin:

Trouble with content security policy

ⅰ亾dé卋堺 提交于 2021-02-11 22:36:58
问题 So i have been trying to use a google programmable search engine script, but i am having trouble with the meta tag. The meta tag that i have included in my is as follows: <meta http-equiv="Content-Security-Policy" content="script-src *.google.com 'self';"> However, i am still getting an error telling me it refused to load the script because it violates the "content-security-policy directive: "script-src 'self'"" I am wondering whether it inherits some sort of settings from somewhere else, as

Trouble with content security policy

落爺英雄遲暮 提交于 2021-02-11 22:23:49
问题 So i have been trying to use a google programmable search engine script, but i am having trouble with the meta tag. The meta tag that i have included in my is as follows: <meta http-equiv="Content-Security-Policy" content="script-src *.google.com 'self';"> However, i am still getting an error telling me it refused to load the script because it violates the "content-security-policy directive: "script-src 'self'"" I am wondering whether it inherits some sort of settings from somewhere else, as

Trouble with content security policy

天大地大妈咪最大 提交于 2021-02-11 22:21:59
问题 So i have been trying to use a google programmable search engine script, but i am having trouble with the meta tag. The meta tag that i have included in my is as follows: <meta http-equiv="Content-Security-Policy" content="script-src *.google.com 'self';"> However, i am still getting an error telling me it refused to load the script because it violates the "content-security-policy directive: "script-src 'self'"" I am wondering whether it inherits some sort of settings from somewhere else, as

Trouble with content security policy

孤街浪徒 提交于 2021-02-11 22:21:58
问题 So i have been trying to use a google programmable search engine script, but i am having trouble with the meta tag. The meta tag that i have included in my is as follows: <meta http-equiv="Content-Security-Policy" content="script-src *.google.com 'self';"> However, i am still getting an error telling me it refused to load the script because it violates the "content-security-policy directive: "script-src 'self'"" I am wondering whether it inherits some sort of settings from somewhere else, as

Trouble with content security policy

荒凉一梦 提交于 2021-02-11 22:18:00
问题 So i have been trying to use a google programmable search engine script, but i am having trouble with the meta tag. The meta tag that i have included in my is as follows: <meta http-equiv="Content-Security-Policy" content="script-src *.google.com 'self';"> However, i am still getting an error telling me it refused to load the script because it violates the "content-security-policy directive: "script-src 'self'"" I am wondering whether it inherits some sort of settings from somewhere else, as

Trouble with content security policy

孤人 提交于 2021-02-11 22:16:26
问题 So i have been trying to use a google programmable search engine script, but i am having trouble with the meta tag. The meta tag that i have included in my is as follows: <meta http-equiv="Content-Security-Policy" content="script-src *.google.com 'self';"> However, i am still getting an error telling me it refused to load the script because it violates the "content-security-policy directive: "script-src 'self'"" I am wondering whether it inherits some sort of settings from somewhere else, as

Chrome Extension and Jenkins URL's

痴心易碎 提交于 2021-02-10 19:33:54
问题 I'm currently trying to develop a chrome extension which is supposed to display data from different Jenkins servers. The url to the jenkins server is being entered by the user. So basically what I need is being able to access any kind of jenkins url. My problem is that Chrome's Content Security Policy only allows you to access domains which you've registered in the manifest.json like so: "content_security_policy": "script-src 'self' http://localhost:8080/; object-src 'self'" . But since

Chrome Extension and Jenkins URL's

落爺英雄遲暮 提交于 2021-02-10 19:32:50
问题 I'm currently trying to develop a chrome extension which is supposed to display data from different Jenkins servers. The url to the jenkins server is being entered by the user. So basically what I need is being able to access any kind of jenkins url. My problem is that Chrome's Content Security Policy only allows you to access domains which you've registered in the manifest.json like so: "content_security_policy": "script-src 'self' http://localhost:8080/; object-src 'self'" . But since

Opening a PDF embedded in iframe in chrome with content security policy > plugin-types

可紊 提交于 2021-02-08 14:58:44
问题 I have the CSP (Content-security-policy) plugin-types policy set to white-list pdf type as below. When trying to open a PDF file in iframe with src attribute, It is working well with browsers IE 11, and Firefox 47+ but failing in Chrome 50+. What else is required to make it working in chrome? Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval'; object-src 'self'; style-src 'self'; frame-src 'self' plugin-types application/pdf; Error in chrome console