Dangerous Cache-Control headers
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- nginx
- Domain
- infrastructure
Research direction
Locate the nginx reverse-proxy configuration containing the shown Cache-Control directive and inspect how it applies to non-crawler responses. Confirm the intended caching behavior, then verify that ordinary browser responses no longer receive a one-year cache policy.
Written by the indexing model from the issue text.
Description
The nginx reverse proxy configuration sets a dangerous Cache-Control header that likely isn't intended for most users.
add_header Cache-Control "public,max-age=31536000";
For non-crawler users, this directs their browser to cache the response for a year.
In my case, the webpages in my app are now refusing to update in client browsers because of this long cache policy. I'm trying to alleviate the issue by modifying the response etag, but in the end, it's up to the browser to decide to revalidate the cache even though the cache expiration is a year.
- Dominant language
- No language data
- Stars
- 28
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
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.
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
copse-dev/agent-pane#2953 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
simonw/sqlite-utils#872 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
danielmiessler/LifeOS#2215 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·