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. */ }
economic

Iran's Rial Hits Record Low as US Deliberates Next Steps Amid Currency Crisis

| Iran Conflict

Iran's rial plunged to a record low against the dollar as the United States deliberates its next steps in the ongoing war, reflecting severe economic pressure from compounding sanctions and the protracted conflict. Iran International is running a live blog covering the currency collapse, which analysts attribute to the dual shock of international financial isolation and war-driven capital flight. The currency freefall deepens domestic economic hardship and intensifies pressure on the Pezeshkian government.

Sources

View full Iran Conflict dashboard