For the static content that we render, we should determine appropriate cache headers to return and make sure we're returning them, so that caching reverse proxies and CDNs can reduce load on Coder.

Many systems are designed to be content-addressable, so that generated files can be cached indefinitely, with only an index page needing to be served without caching (or with caching but requiring revalidation with an ETag or timestamp).

We would likely need to investigate how next export content should be served when added to an S3 or GCS bucket (i.e. what headers are added), and replicate those in our server.