liu1004010308 opened a new issue, #12346:
URL: https://github.com/apache/apisix/issues/12346
### Description
Hi team,
I encountered an issue where setting the X-Real-IP header in the
proxy-rewrite plugin has no effect.
Environment
APISIX version: 3.3
Deployment mode: e.g., standalone / etcd
Plugins used: proxy-rewrite
Upstream: [optional]
Configuration
config.yaml:
> real_ip_header: X-Real-IP
real_ip_recursive: "off"
real_ip_from: - 0.0.0.0/0 - 127.0.0.1
Route configuration:
> "plugins": {
"proxy-rewrite": {
"headers": {
"Connection": "upgrade",
"Host": "$host",
"X-Forwarded-For": "$proxy_add_x_forwarded_for",
"Upgrade": "$http_upgrade",
"X-Real-IP": "1.1.1.1"
},
"use_real_request_uri_unsafe": true
}
}
Expected Behavior
I expected that setting "X-Real-IP": "1.1.1.1" in the route's headers would
allow me to override the IP seen by APISIX as the client's real IP
Actual Behavior
Regardless of the value I set for X-Real-IP in the route configuration, the
final client IP seen by APISIX always reflects the actual remote_addr, not the
spoofed header.
Question
Is this expected behavior? Shouldn't setting the X-Real-IP in proxy-rewrite?
Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
