Sevalla Changelog #0076 Control Static Site Headers
Define your static site's headers in your code. Keep it version-controlled and reviewable.
Establishing connection…
Signal detected.
Link established.
Baud here with a 2400 Sevalla changelog transmission.
Updates in this transmission:
One update shipped. Small surface area. Real impact for teams running production static workloads.
Let's take a look.
Static sites: control headers…finally#
This one's been on the list for a while, and it's been a frequent ask. Thanks for the patience and for keeping the pressure on.
You can now define custom HTTP headers for static sites using a _headers file in your repo. The syntax is modeled on Netlify's _headers file, so most existing files should work as a drop-in or with minor tweaks. We're not aiming for 100% parity, but the common cases all behave the same way.
What's supported
- Match routes with wildcards like
/*or/assets/* - Use placeholders like
/:slugfor dynamic paths - Combine rules automatically when multiple match
Useful for the usual things: CSP and HSTS, cache policies for static assets, CORS across environments, all defined alongside your code, versioned with the rest of the repo.
What you can't override
A few headers stay managed by the platform (Content-Encoding, Server, Transfer-Encoding, and a few others) since overriding them tends to break things in non-obvious ways.
Check out the Static Sites - Headers documentation.
Behind the scenes#
Not everything we ship shows up as a feature.
Right now, we're focused on tightening the systems behind the platform. The goal is simple: fewer edge cases, more predictable behavior in production.
That includes:
- improving reliability and scalability across the platform
- standardizing parts of our infrastructure's deployment
- automating internal processes so we can move faster without breaking things
This work isn't flashy, but it matters.
It's how we make sure Sevalla holds up under real production workloads, not just demos.
Transmission complete#
Custom headers for static sites. Defined in code. Applied automatically. No further configuration required.
More improvements on the way.
Awaiting next transmission.
Link closed.