I’m testing out the awesome CSP that was added ( Mitigate XSS Attacks with Content Security Policy ). I’ve currently had it in report only mode since release, and am seeing a large number of CSP Violation: 'inline' reports on /logs that are violating the script-src. I’m guessing the best way to avoid…

I can’t recall where we are on logster @pmusaraj ? Also make sure you update to latest and do a full container rebuild at the command line.

[Bild] codinghorror: Also make sure you update to latest and do a full container rebuild at the command line. Ahh, does the web upgrade not cover quite as much? I can login tonight and get an upgrade done via SSH.

These 'inline' CSP violation errors are in most cases false positives. If you can post the contents of the env tab from the log, that will have some more details, but I’m fairly certain this is coming from an extension. The vast majority of CSP report violations logged are false positives, and we w…

[Bild] pmusaraj: and we will shortly turn off reporting by default, because it’s not very helpful We still haven’t done this? We need to get this done..

[Bild] pmusaraj: These 'inline' CSP violation errors are in most cases false positives. If you can post the contents of the env tab from the log, that will have some more details, but I’m fairly certain this is coming from an extension. The vast majority of CSP report violations logged are fals…

Ah, I see that violation in the Chrome console as well (but not on Safari or Firefox) when visiting gamingexodus.com . You can either turn on CSP in full or turn on violation report logging temporarily, Chrome needs one of the two to display more details about the source of the CSP violation.

Just toggled the full CSP on. Oddly enough, I’m not seeing any of the errors now. Do I need to rebuild the Docker image after enabling the full CSP option? As an aside, I think the two CSP options should be mutually exclusive. You should only be able to select report only CSP, full CSP, or no CSP. …

Nur CSP-Verstöße melden

Unterstützung

pmusaraj (Penar Musaraj) 15. Januar 2019 um 15:44 8

CSP violation reporting is now off by default as of FEATURE: enable CSP by default on new sites (#6873) · discourse/discourse@1c1fd20 · GitHub

Thema		Antworten	Aufrufe
Mitigate XSS Attacks with Content Security Policy Site Management how-to , content-security-policy	30	25672	13. Juni 2023
After upgrade the content security policy script src for GTM Data & reporting	4	1978	13. April 2021
Discourse refused to load with CSP policy error after rebuild Support	4	2956	8. Mai 2019
How to fix problem with CSP Support	8	6865	9. März 2022
A user cannot login due to CSP issue Support	4	559	30. September 2023

Nur CSP-Verstöße melden

Verwandte Themen