How can I determine what “inline script” Firefox console is complaining about regarding my Content...

I set up a Content Security Policy and Chrome is perfectly happy with it. Firefox though displays these errors in the console.

These line numbers do not point to script (e.g. 1:1 is just <!DOCTYPE html>).

How can I determine what script Firefox is complaining about?

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). xxx.com:1:1    

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). xxx.com:3:4629

asked Nov 21 '18 at 18:35

Luke Williams

1,2861128

add a comment |

I set up a Content Security Policy and Chrome is perfectly happy with it. Firefox though displays these errors in the console.

These line numbers do not point to script (e.g. 1:1 is just <!DOCTYPE html>).

How can I determine what script Firefox is complaining about?

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). xxx.com:1:1    

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). xxx.com:3:4629

asked Nov 21 '18 at 18:35

Luke Williams

1,2861128

add a comment |

I set up a Content Security Policy and Chrome is perfectly happy with it. Firefox though displays these errors in the console.

These line numbers do not point to script (e.g. 1:1 is just <!DOCTYPE html>).

How can I determine what script Firefox is complaining about?

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). xxx.com:1:1    

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). xxx.com:3:4629

asked Nov 21 '18 at 18:35

Luke Williams

1,2861128

I set up a Content Security Policy and Chrome is perfectly happy with it. Firefox though displays these errors in the console.

These line numbers do not point to script (e.g. 1:1 is just <!DOCTYPE html>).

How can I determine what script Firefox is complaining about?

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). xxx.com:1:1    

Content Security Policy: The page’s settings blocked the loading of a resource at inline (“script-src”). xxx.com:3:4629

security firefox

asked Nov 21 '18 at 18:35

Luke Williams

1,2861128

asked Nov 21 '18 at 18:35

Luke Williams

1,2861128

asked Nov 21 '18 at 18:35

Luke Williams

1,2861128

asked Nov 21 '18 at 18:35

Luke Williams

1,2861128

asked Nov 21 '18 at 18:35

Luke Williams

1,2861128

add a comment |

1 Answer
1

active

oldest

votes

This is a NoScript issue. Tell NoScript to allow scripts.

It is related to where the document lives and apparently has nothing to do with the document's content.

I can reproduce the issue on my local filesystem (file:///tmp/test.html) with this tiny HTML snippet:

<html><head>

  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>

</head><body>test</body>

</html>

^{(Note the lack of scripts. The <meta> tag only exists to suppress the character encoding complaint.)}

When I tell NoScript to allow scripts from file: and refresh the page, the policy notice goes away.

answered Dec 16 '18 at 23:33

Adam Katz

5,93913654

add a comment |

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
});

}
});

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53418542%2fhow-can-i-determine-what-inline-script-firefox-console-is-complaining-about-re%23new-answer', 'question_page');
}
);

Post as a guest

Name

Required, but never shown

1 Answer
1

active

oldest

votes

1 Answer
1

active

oldest

votes

This is a NoScript issue. Tell NoScript to allow scripts.

It is related to where the document lives and apparently has nothing to do with the document's content.

I can reproduce the issue on my local filesystem (file:///tmp/test.html) with this tiny HTML snippet:

<html><head>

  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>

</head><body>test</body>

</html>

^{(Note the lack of scripts. The <meta> tag only exists to suppress the character encoding complaint.)}

When I tell NoScript to allow scripts from file: and refresh the page, the policy notice goes away.

answered Dec 16 '18 at 23:33

Adam Katz

5,93913654

add a comment |

This is a NoScript issue. Tell NoScript to allow scripts.

It is related to where the document lives and apparently has nothing to do with the document's content.

I can reproduce the issue on my local filesystem (file:///tmp/test.html) with this tiny HTML snippet:

<html><head>

  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>

</head><body>test</body>

</html>

^{(Note the lack of scripts. The <meta> tag only exists to suppress the character encoding complaint.)}

When I tell NoScript to allow scripts from file: and refresh the page, the policy notice goes away.

answered Dec 16 '18 at 23:33

Adam Katz

5,93913654

add a comment |

This is a NoScript issue. Tell NoScript to allow scripts.

It is related to where the document lives and apparently has nothing to do with the document's content.

I can reproduce the issue on my local filesystem (file:///tmp/test.html) with this tiny HTML snippet:

<html><head>

  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>

</head><body>test</body>

</html>

^{(Note the lack of scripts. The <meta> tag only exists to suppress the character encoding complaint.)}

When I tell NoScript to allow scripts from file: and refresh the page, the policy notice goes away.

answered Dec 16 '18 at 23:33

Adam Katz

5,93913654

This is a NoScript issue. Tell NoScript to allow scripts.

It is related to where the document lives and apparently has nothing to do with the document's content.

I can reproduce the issue on my local filesystem (file:///tmp/test.html) with this tiny HTML snippet:

<html><head>

  <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/>

</head><body>test</body>

</html>

^{(Note the lack of scripts. The <meta> tag only exists to suppress the character encoding complaint.)}

When I tell NoScript to allow scripts from file: and refresh the page, the policy notice goes away.

answered Dec 16 '18 at 23:33

Adam Katz

5,93913654

answered Dec 16 '18 at 23:33

Adam Katz

5,93913654

answered Dec 16 '18 at 23:33

Adam Katz

5,93913654

answered Dec 16 '18 at 23:33

Adam Katz

5,93913654

add a comment |

draft saved

draft discarded

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.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Post as a guest

Name

Required, but never shown

Name

Required, but never shown

Name

Required, but never shown

This page is only for reference, If you need detailed information, please check here

Search This Blog

Ufyukyu