Custom response headers for a static site
What response headers control on a static site, from browser caching through to security policy, and how your static site is served on Voroa at present.
What this covers
A static site has no code running to set its own headers, so the server has to be told what to send. Two groups matter. Caching headers decide how long a browser keeps a file before asking again, which is the difference between a repeat visit being instant and being a full download; the usual pattern is a long cache for fingerprinted assets and no cache for the HTML that points at them. Security headers tell the browser what your page is allowed to do, such as which sources may load scripts and whether the site may be shown inside a frame elsewhere.
Setting custom response headers for a static site is not available on Voroa today. Static sites are served with the platform’s defaults.