WPIntell

Source evidence

Concerns about nginx deployment

No unsafe-inline · support · 2026-05-20T20:50:00+00:00

complaintsentiment
highseverity
0.91relevance
0replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

5 / 35 rows with source links

14.3% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

30 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
DaddyJ unresolved
Hi, Giuseppe! Kudos to you for trying to resolve an issue that should really be of top concern to the entire WordPress ecosystem! I’d like to install “No unsafe inline”, but I am concerned about whether it will work for my specific case. My site of concern is hosted on an Ngnix server (Dreamhost’s DreamPress service). According to Dreamhost Support, since Ngnix does not allow directory-level config files (that I could modify myself), the only way to modify the CSP is to submit a support request to Dreamhost technical staff and wait for them to deploy it! This sounds like a big bottleneck, particularly in the early stages. And it seems like the CSP will need to be constantly updated every time a plugin updates or an author adds inline JS or CSS to a page. And then I found this unresolved support query from November 2024: https://wordpress.org/support/topic/activating-report-only-mode-crashes-website-on-nginx/ Do you have more recent insight on nginx compatibility?

Comments

0 shown

No comments were stored for this source.