playframework / playframework/play-ws
How does stale-while-revalidate work with POST / unsafe methods?
Open
Nobody has claimed this yet.
status:backlog
- Dominant language
- Scala
- Stars
- 224
- Forks
- 92
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 28
Description
This may be academic considering most people only want to store on GET, but for the record:
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
Read play-ahc-ws-standalone/src/main/scala/play/api/libs/ws/ahc/cache/CachingAsyncHttpClient.scala at line 121 and trace how stale-while-revalidate handles POST and other unsafe methods. Clarify the expected behavior and document the conclusion or add a focused test if the project provides an appropriate cache test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- scala
- Domain
- networking
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100