spring-cloud / spring-cloud/spring-cloud-gateway
Add option to ignore `IllegalArgumentException` if discovery locator enabled
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.
If an illegal appname is registered on Eureka, such as "lb:// ", it will cause the service to fail to start and throw "Illegal character in authority at index 5: lb://"
Describe the solution you'd like
filter out illegal appnames during startup
Describe alternatives you've considered
When registering a service for the eureka client, if it is an illegal uri, block the registration of the service and throw an exception
Additional context
Add any other context or screenshots about the feature request here.
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 discovery locator startup path where Eureka app names become URIs and the IllegalArgumentException is raised. Clarify whether invalid names should be filtered during startup or rejected during registration, then verify the chosen behavior for invalid and valid registrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100