Support Cache-Control: immutable
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 505
- Forks
- 149
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
There is a draft extension added by facebook called Cache-Control: immutable. If a response is served as immutable then that means it will never ever change no matter what. It seems like it would be useful to support this.
Ideally if a response has been marked immutable we can just skip any sort of Etag or freshness handling and just blindly serve the response.
More information here: https://bitsup.blogspot.com/2016/05/cache-control-immutable.html
Contributor guide
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
No file, test, or entry point is named in the issue. Start by locating Cache-Control parsing and the ETag or freshness handling, then verify that an immutable response bypasses those checks and is served unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100