Add cache-control headers when serving static files
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 39
- Avg merge
- 4d 11h
- Merged PRs (30d)
- 4
Description
We currently don't set cache-control headers, this causes the browser to always send requests when it could avoid doing so.
The new header would be added following how the ETag header is integrated.
The console build system will need to hash the assets, this is a minor change since it is fully supported by Webpack.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the static-file serving code and the existing ETag integration, then inspect the console build system's Webpack configuration for asset hashing. Done means static assets receive cache-control headers and the generated assets are hashed so browsers can reuse them safely.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, webpack
- Domain
- build-system, frontend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100