spring-cloud/spring-cloud-gateway

Add option to ignore `IllegalArgumentException` if discovery locator enabled

Open

#2,952 创建于 2023年5月11日

在 GitHub 查看
 (3 评论) (0 反应) (0 负责人)Java (4,284 star) (3,204 fork)batch import
enhancementhelp wanted

描述

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.

贡献者指南

技术栈
java
领域
backendapi
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
half day
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
JavaSpring Cloud Gateway basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
60
研究方向
Look into the DiscoveryClientRouteDefinitionLocator class where Eureka service discovery is integrated. Investigate how appnames are validated and where the IllegalArgumentException is thrown. Consider adding a configuration option to ignore or filter out illegal appnames during startup. Check existing tests for route definition locators.