spring-cloud / spring-cloud/spring-cloud-gateway
Support for per-route-timeouts in gateway-server-webmvc
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Is your feature request related to a problem? Please describe.
We recently switched from spring-cloud-starter-gateway to spring-cloud-starter-gateway-server-webmvc for various reasons.
We were able to specify per route timeouts before via application.properties (spring.cloud.gateway.routes[x].metadata.response-timeout, as described in per-route-timeouts).
Now we can't use per-route-timeouts anymore, so instead we have to use the highest previously used response-timeout as a global configuration via spring.http.client.read-timeout.
Describe the solution you'd like
A possibility to define per route timeouts via Java Routes API.
Describe alternatives you've considered
- Manipulating the request through HandlerFilterFunction
- Switching to Proxy Exchange Gateway
Additional context
This is a feature request similar to the "bug" reported in #3378
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 with the Java Routes API and compare its route configuration with the existing application.properties per-route timeout behavior described in the issue. Review the HandlerFilterFunction and Proxy Exchange Gateway alternatives for context. Done means Java route definitions can specify distinct response timeouts for individual routes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100