spring-cloud / spring-cloud/spring-cloud-gateway
When routes.predicates.RemoteAddr be set, and request was forbidden, the result is not clear enough.
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.
When I set RemoteAddr config in routes.predicates, if request was forbidden by ip, the result was not clear enough ,just show 404, but I want more clear infomation,like 403 or other some info.
Describe the solution you'd like
I hope when request was forbidden by RemoteAddr, give a callback or some clear exception, so we can handle it.
Describe alternatives you've considered
I knew io.netty.handler.ipfilter.IpFilterRuleType have another value REJECT , but I didn't find it in Spring Cloud Gateway, maybe could consider it in Spring Cloud Gateway.
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 tracing the routes.predicates.RemoteAddr handling and its integration with Netty's IP filter rules. Compare the current forbidden-request behavior with the REJECT option mentioned in the issue. Before implementation, clarify whether the expected result is a 403 status, an exception, or a callback, then add coverage for the agreed behavior.
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
- Needs clarification
- Newbie friendliness
- 25/100