and extracts the following text as a script body — the dev server then fails its dependency scan with `Expected ";" but found "non"` from the words "non-allowlisted hosts", which breaks e2e. So, what this buys, so nobody reads more or less into it: blocks external `script src=` from non-allowlisted hosts blocks injected inline scripts — each one is pinned by hash blocks fetch/XHR/WebSocket exfiltration (connect-src allowlist) blocks form-action, base-uri, object-src vectors does not stop image-based exfiltration — img-src must allow https: because event media comes from arbitrary publishers' og:image The cost of hashing is that an inline script edited after the hashes are computed is silently refused by the browser. That is why the violation reporter below exists: report-uri/report-to are ignored in a meta element and Pages serves no CSP header, so violations are caught in-page and sent to PostHog instead (src/lib/csp-report.ts, #241). frame-ancestors is deliberately NOT in this string: it is ignored in a meta element and browsers log a warning about it on every page load. It lives in public/_headers instead, ready for a CDN in front of Pages. X-Frame-Options (set there too) is the clickjacking control that actually applies today. */ }
strike-claim

Houthis Claim Attack on Aramco Facilities; Saudi Coalition Calls Claim 'Misleading'

| Yemen Conflict

Houthi forces claimed responsibility for an attack on Saudi Aramco oil facilities as the Yemen conflict continued to escalate, citing the strikes as retaliation for the Saudi-led coalition's military operations. The Saudi-led coalition dismissed the Houthi claim as 'misleading', characterizing it as propaganda intended to exaggerate the group's capabilities and impact on Saudi infrastructure.

Media

📄 Read article
Houthis claim attack on Aramco facilities as Yemen conflict escalates — New York Times

Sources

View full Yemen Conflict dashboard