ETag vs headers
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Describe the bug
The API returns conflicting headers: ETag is provided for resource validation, but Cache-Control is set to no-store. This prevents the client from caching and validating the resource, rendering the ETag ineffective.
To Reproduce
- Make a request to any endpoint returning
ETag. - Observe the response headers:
Cache-Control:"no-cache, no-store, must-revalidate". - Notice that caching is prevented despite ETag being present.
Expected behavior
Either remove the no-store directive to allow caching with validation or remove the ETag header if caching is not intended.
Client details:
- OS: Any
- Browser: Any
- Version: Any
- Device: Any
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
Start by locating the endpoint response code that sets both ETag and Cache-Control, then reproduce the issue against an endpoint returning ETag. Confirm the intended caching policy with the project maintainers; done means the response headers no longer conflict and the behavior is covered by the relevant test if one exists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100