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.