# Cloudflare Pages headers. # # Everything under /_astro/ and /fonts/ is content-hashed or versioned with the deploy, so it can be # cached forever. HTML cannot: it is how a visitor discovers there is a new build at all. /_astro/* Cache-Control: public, max-age=31536000, immutable /fonts/* Cache-Control: public, max-age=31536000, immutable Access-Control-Allow-Origin: * # The guide as plain text, for agents. A charset, since Pages guesses none for these, and a client # reading from another origin is the point of them. /docs/*.md Content-Type: text/markdown; charset=utf-8 Access-Control-Allow-Origin: * /llms.txt Content-Type: text/plain; charset=utf-8 Access-Control-Allow-Origin: * /llms-full.txt Content-Type: text/plain; charset=utf-8 Access-Control-Allow-Origin: * # Text, so `irm` hands `iex` a script rather than bytes /install.ps1 Content-Type: text/plain; charset=utf-8 /* Cache-Control: public, max-age=0, must-revalidate X-Content-Type-Options: nosniff Referrer-Policy: strict-origin-when-cross-origin # The site runs its own scripts and nothing else. No analytics, no embeds, no third-party origins # — which is the same promise the product makes, and the only way to keep it is to forbid them. # # 'wasm-unsafe-eval' is load-bearing: the demo player parses the terminal with a Rust VT compiled # to WebAssembly, and a script-src without it blocks WebAssembly.instantiate outright — the player # throws and every demo renders as an empty box. It grants wasm compilation ONLY; it does not # permit eval() or any other string-to-code path, which is why it is not 'unsafe-eval'. The # third-party promise above is untouched by it. Content-Security-Policy: default-src 'self'; script-src 'self' 'unsafe-inline' 'wasm-unsafe-eval'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self'; connect-src 'self'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'