caelum0x 9afd87e95f fix(csp): correct stale sha256 hash blocking the X ads conversion pixel
site/_headers allowlisted the inline twq() pixel script by a sha256 hash
that no longer matched the actual script content (byte-for-byte hash
mismatch, likely from a prior edit to TWITTER_PIXEL_SNIPPET in
worker/index.js that was never re-hashed). The browser silently blocked
the inline script on every page load, so static.ads-twitter.com/uwt.js
never loaded and the adsct conversion beacon never fired. Same bug
class independently found on bidstage.app and ereboslab.com today
(missing CSP allowlist entries), this time via a drifted hash instead
of a missing domain.

Recomputed the hash from the live-rendered inline script and verified
in-browser: uwt.js now loads (200) and the adsct beacon fires with no
CSP violations. Added a comment at the snippet definition so future
edits re-hash it instead of drifting again.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
2026-10-24 22:03:45 +03:00
..