Cache-Control header / past Expires in inner exchange's response.
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 1.3k
- Forks
- 125
- PR merge metrics
- No merged PRs in 30d
Description
I've seen SXG inner exchange's response headers containing:
Cache-Control: no-cache, no-store
Expires: <past date>
How should we handle these cases?
- Option 1) Add them to the banned headers list
- Option 2) As proposed by @mnot in #326, enforce the response cacheability algorithm in verification steps.
My preference is Option 2.
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 reading the response cacheability algorithm in RFC 7234 and the discussion in issue #326. Compare that approach with adding Cache-Control and Expires to the banned headers list. Done means the project has a decided handling rule for these inner-exchange response headers and the verification requirements are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100