Add Caching Headers
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 14
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
All requests going through UPWARD PHP, including those for static files, include `Cache-Control: no-store, no-cache, must-revalidate`. There needs to be some better handling of response caching, especially for File & Directory Resolvers
- Determine what the appropriate caching policy should be
- What should the cache lifetime be?
- Should we include an ETag, or are those passé?
- In what cases should a cache header be included or not?
- Add the appropriate cache headers
- What options should there be for disabling or clearing these headers (eg for development vs production)?
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 reviewing the File and Directory Resolvers and how UPWARD PHP currently sets response headers. Determine the caching policy, including lifetimes, ETags, and when headers apply, then define options for disabling or clearing them in development versus production. Done means requests receive the appropriate cache headers under the selected policy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100