spring-cloud / spring-cloud/spring-cloud-gateway
Add cache predicate for ReadBodyPredicateFactory
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Some body shouldn't be cached, for instance chunked-transfer: encoded requests or content-length: XX where XX could be greater than 64K, 128K or even 1024K.
The current predicate only tests the body but the incoming headers should be tested too.
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 at ReadBodyPredicateFactory and inspect how its current predicate evaluates the body. Trace how incoming headers are available, then make the cache decision account for chunked-transfer encoding and content-length values; done means these requests are excluded from caching while eligible bodies retain the existing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100