spring-cloud / spring-cloud/spring-cloud-gateway
Have the ability to hide @RequestMapping endpoints that are meant to be used by forward scheme
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 4.9k
- Forks
- 3.5k
- Avg merge
- 20h 57m
- Merged PRs (30d)
- 8
Description
Sometimes we want to have RequestMappings only to be used internally by the Gateway. For example when we create one fallback endpoint to be used by the HystrixGatewayFilterFactory or by using uri forward:/my-endpoint in another route. Right now even if a route is not declared in the RouteLocator is still reachable if that endpoint is declared by means of @RequestMapping. I think this should be configurable for people who want to have more control on which routes should be exposed in the Gateway and only want to made available the routes that were declared in the Gateway Configuration.
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 how @RequestMapping endpoints and RouteLocator routes are exposed by the gateway, including forward:/ routes and the HystrixGatewayFilterFactory example. Define the configuration boundary that hides internal endpoints while preserving declared gateway routes, then verify both access paths with the relevant gateway tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring, spring-boot
- Domain
- api, backend, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100