litespeedtech / litespeedtech/lscache_wp
The Cache-Control header is removed from cache hits
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 257
- Forks
- 123
- PR merge metrics
- No merged PRs in 30d
Description
Response without cache, e.g. a POST request
```http
Cache-Control: no-cache, no-store, must-revalidate, max-age=0
```
with cache, e.g. a GET request: the `Cache-Control` header is missing meaning
> This response allows caches to assign their own freshness lifetimes to it.
Please advise. It is intentional?
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 reproducing the reported difference between the POST response and the cached GET response, then trace the plugin's handling of the Cache-Control header for cache hits. The issue does not name a file or test; done should mean the intended header behavior is established and the cached response no longer permits unintended freshness lifetimes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100