axeon
axeon
> I am unable to replicate this issue. I [plugged your regex into](https://github.com/spring-cloud/spring-cloud-gateway/blob/4b6fb4c0fbfb4a770715ccf2826359977c2a15f7/spring-cloud-gateway-server/src/test/resources/application.yml#L18) my existing [integration test](https://github.com/spring-cloud/spring-cloud-gateway/blob/4b6fb4c0fbfb4a770715ccf2826359977c2a15f7/spring-cloud-gateway-server/src/test/java/org/springframework/cloud/gateway/test/GatewayIntegrationTests.java#L123-L141) and it passed. The local test uses localhost 127.0.0.1, which your regex matches...
> > Always forward request.getRemoteAddress() as X-Forwarded-For by default, without any restriction. > > This will not happen. See [this security advisory](https://spring.io/security/cve-2025-41235) for details. In the official preset scenarios of...
> > Currently, for restore forwarding of the real client IP, I have to set trusted-proxies to [\s\S]*, which defeats its purpose. > > Doesn't this get you the behavior...
pull request https://github.com/spring-cloud/spring-cloud-gateway/pull/3819 fix(gateway): optimize XForwardedHeadersFilter logic - Remove @Conditional annotation from xForwardedHeadersFilter bean - Set default trustedProxies regex(internal ips) in GatewayProperties - Refactor XForwardedHeadersFilter to improve readability and performance...
@spencergibb Thank you very much for your response. In the User → SCA → MicroService scenario, the correct logic should be: 1. By default, UserIp should be forwarded as X-Forwarded-For....
> > Hello folks! > > I recently had to update the **spring-cloud-starter-gateway** library to version **4.1.8** due to a vulnerability reported by internal company tools in previous versions. After...
Refer to PR[#3819](https://github.com/spring-cloud/spring-cloud-gateway/pull/3819). Trust me, this is the best solution! If possible, please reopen it. > Original poster has already outlined the same issues regarding incorrect trusted proxy usage [#3818...
不知道alibaba在搞什么鬼。。。 现在大部分人的版本都被控制在了2023.0.1.2上了。
！！！非常希望能够支持像之前一样的配置方式！！！ 当前的config.import语法的手工配置项太多，且复杂。 我们当前项目通过统一的配置文件，大幅度简化配置，打包到镜像之后，很容易通过环境变量适配多个环境。 比如如下的bootstrap.yml文件。 ```yaml project: name: @project.name@ version: @project.version@ spring: application: name: ${project.name} cloud: nacos: server-addr: ${NACOS_SERVER} username: ${NACOS_USERNAME} password: ${NACOS_PASSWORD} config: namespace: ${NACOS_NAMESPACE} file-extension: yaml discovery: namespace: ${spring.cloud.nacos.config.namespace}...