Google fonts not loading despite security policy setting
I want to load fonts from google, but it doesn't work, tried different variations of Content-Security-Policy, but it continues to fail. With the configuration below, I'm getting:
because it violates the following Content Security Policy directive:
"default-src 'self'". Note that 'style-src' was not explicitly set, so
'default-src' is used as a fallback.
Does this error even make sense? I'm setting the style-src property.
What am I doing wrong? Thanks.
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' https://fonts.googleapis.com; font-src 'self' https://fonts.googleapis.com;">
<link rel="icon" type="image/x-icon" href="~/favicon.ico" />
<link rel="shortcut icon" type="image/x-icon" href="~/favicon.ico" />
<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:400,700">
<link rel="stylesheet" href="~/lib/materialize/css/materialize.css">
<link rel="stylesheet" href="~/css/site.css" />
html meta-tags content-security-policy google-font-api
add a comment |
I want to load fonts from google, but it doesn't work, tried different variations of Content-Security-Policy, but it continues to fail. With the configuration below, I'm getting:
because it violates the following Content Security Policy directive:
"default-src 'self'". Note that 'style-src' was not explicitly set, so
'default-src' is used as a fallback.
Does this error even make sense? I'm setting the style-src property.
What am I doing wrong? Thanks.
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' https://fonts.googleapis.com; font-src 'self' https://fonts.googleapis.com;">
<link rel="icon" type="image/x-icon" href="~/favicon.ico" />
<link rel="shortcut icon" type="image/x-icon" href="~/favicon.ico" />
<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:400,700">
<link rel="stylesheet" href="~/lib/materialize/css/materialize.css">
<link rel="stylesheet" href="~/css/site.css" />
html meta-tags content-security-policy google-font-api
post your CSP config, please
– vanelizarov
Nov 12 at 15:04
I did... <meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' fonts.googleapis.com; font-src 'self' fonts.googleapis.com;">
– Naner
Nov 12 at 15:04
check this stackoverflow.com/questions/42369075/…
– Ali
Nov 12 at 15:09
Thank you @Ali, it makes sense, but it didn't work, still getting the same error: "because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'style-src' was not explicitly set, so 'default-src' is used as a fallback."
– Naner
Nov 12 at 15:27
Alright, found it. The header is been overwritten by custom code in the application. I'm sorry I didn't find it sooner. Anyone going off the IdentityServer4 example might come across this issue.
– Naner
Nov 12 at 15:41
add a comment |
I want to load fonts from google, but it doesn't work, tried different variations of Content-Security-Policy, but it continues to fail. With the configuration below, I'm getting:
because it violates the following Content Security Policy directive:
"default-src 'self'". Note that 'style-src' was not explicitly set, so
'default-src' is used as a fallback.
Does this error even make sense? I'm setting the style-src property.
What am I doing wrong? Thanks.
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' https://fonts.googleapis.com; font-src 'self' https://fonts.googleapis.com;">
<link rel="icon" type="image/x-icon" href="~/favicon.ico" />
<link rel="shortcut icon" type="image/x-icon" href="~/favicon.ico" />
<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:400,700">
<link rel="stylesheet" href="~/lib/materialize/css/materialize.css">
<link rel="stylesheet" href="~/css/site.css" />
html meta-tags content-security-policy google-font-api
I want to load fonts from google, but it doesn't work, tried different variations of Content-Security-Policy, but it continues to fail. With the configuration below, I'm getting:
because it violates the following Content Security Policy directive:
"default-src 'self'". Note that 'style-src' was not explicitly set, so
'default-src' is used as a fallback.
Does this error even make sense? I'm setting the style-src property.
What am I doing wrong? Thanks.
<meta charset="utf-8" />
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' https://fonts.googleapis.com; font-src 'self' https://fonts.googleapis.com;">
<link rel="icon" type="image/x-icon" href="~/favicon.ico" />
<link rel="shortcut icon" type="image/x-icon" href="~/favicon.ico" />
<link rel="stylesheet" href="https://fonts.googleapis.com/icon?family=Material+Icons">
<link rel="stylesheet" href="https://fonts.googleapis.com/css?family=Roboto:400,700">
<link rel="stylesheet" href="~/lib/materialize/css/materialize.css">
<link rel="stylesheet" href="~/css/site.css" />
html meta-tags content-security-policy google-font-api
html meta-tags content-security-policy google-font-api
asked Nov 12 at 15:01
Naner
65042134
65042134
post your CSP config, please
– vanelizarov
Nov 12 at 15:04
I did... <meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' fonts.googleapis.com; font-src 'self' fonts.googleapis.com;">
– Naner
Nov 12 at 15:04
check this stackoverflow.com/questions/42369075/…
– Ali
Nov 12 at 15:09
Thank you @Ali, it makes sense, but it didn't work, still getting the same error: "because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'style-src' was not explicitly set, so 'default-src' is used as a fallback."
– Naner
Nov 12 at 15:27
Alright, found it. The header is been overwritten by custom code in the application. I'm sorry I didn't find it sooner. Anyone going off the IdentityServer4 example might come across this issue.
– Naner
Nov 12 at 15:41
add a comment |
post your CSP config, please
– vanelizarov
Nov 12 at 15:04
I did... <meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' fonts.googleapis.com; font-src 'self' fonts.googleapis.com;">
– Naner
Nov 12 at 15:04
check this stackoverflow.com/questions/42369075/…
– Ali
Nov 12 at 15:09
Thank you @Ali, it makes sense, but it didn't work, still getting the same error: "because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'style-src' was not explicitly set, so 'default-src' is used as a fallback."
– Naner
Nov 12 at 15:27
Alright, found it. The header is been overwritten by custom code in the application. I'm sorry I didn't find it sooner. Anyone going off the IdentityServer4 example might come across this issue.
– Naner
Nov 12 at 15:41
post your CSP config, please
– vanelizarov
Nov 12 at 15:04
post your CSP config, please
– vanelizarov
Nov 12 at 15:04
I did... <meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' fonts.googleapis.com; font-src 'self' fonts.googleapis.com;">
– Naner
Nov 12 at 15:04
I did... <meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' fonts.googleapis.com; font-src 'self' fonts.googleapis.com;">
– Naner
Nov 12 at 15:04
check this stackoverflow.com/questions/42369075/…
– Ali
Nov 12 at 15:09
check this stackoverflow.com/questions/42369075/…
– Ali
Nov 12 at 15:09
Thank you @Ali, it makes sense, but it didn't work, still getting the same error: "because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'style-src' was not explicitly set, so 'default-src' is used as a fallback."
– Naner
Nov 12 at 15:27
Thank you @Ali, it makes sense, but it didn't work, still getting the same error: "because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'style-src' was not explicitly set, so 'default-src' is used as a fallback."
– Naner
Nov 12 at 15:27
Alright, found it. The header is been overwritten by custom code in the application. I'm sorry I didn't find it sooner. Anyone going off the IdentityServer4 example might come across this issue.
– Naner
Nov 12 at 15:41
Alright, found it. The header is been overwritten by custom code in the application. I'm sorry I didn't find it sooner. Anyone going off the IdentityServer4 example might come across this issue.
– Naner
Nov 12 at 15:41
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264841%2fgoogle-fonts-not-loading-despite-security-policy-setting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53264841%2fgoogle-fonts-not-loading-despite-security-policy-setting%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
post your CSP config, please
– vanelizarov
Nov 12 at 15:04
I did... <meta http-equiv="Content-Security-Policy" content="default-src 'self'; style-src 'self' fonts.googleapis.com; font-src 'self' fonts.googleapis.com;">
– Naner
Nov 12 at 15:04
check this stackoverflow.com/questions/42369075/…
– Ali
Nov 12 at 15:09
Thank you @Ali, it makes sense, but it didn't work, still getting the same error: "because it violates the following Content Security Policy directive: "default-src 'self'". Note that 'style-src' was not explicitly set, so 'default-src' is used as a fallback."
– Naner
Nov 12 at 15:27
Alright, found it. The header is been overwritten by custom code in the application. I'm sorry I didn't find it sooner. Anyone going off the IdentityServer4 example might come across this issue.
– Naner
Nov 12 at 15:41