带有cloudflare和ingress-nginx的无效X-Forwarded-For标头



我有一些问题得到正确的IP头。我正在使用以下代理设置:

Cloudflare→亚马逊NLB ->Ingress-nginx(美丽)

my ingress-nginx有如下配置:

config:
use-forwarded-headers: "true"
real-ip-header: "CF-Connecting-IP"
forwarded-for-header: "CF-Connecting-IP"
set-real-ip-from: "0.0.0.0/0"
proxy-buffer-size: "16k"
proxy-buffers-number: "8"

由于某些原因,x-real-ip报头是正确的,但x-forwarded-for报头不是:

REMOTE ADDR: 127.0.0.1
X FORWARDED FOR: 10.0.102.38 <- Wrong
X-REAL-IP: xx.xxx.xxx.xxx <- Correct

ingress-nginx loadbalancer (NLB) has:

External Traffic Policy:  Local

根据文档。以及以下注释:

service.beta.kubernetes.io/aws-load-balancer-backend-protocol: tcp
service.beta.kubernetes.io/aws-load-balancer-connection-idle-timeout: 3600
service.beta.kubernetes.io/aws-load-balancer-proxy-protocol: *
service.beta.kubernetes.io/aws-load-balancer-ssl-cert: xxxx
service.beta.kubernetes.io/aws-load-balancer-ssl-ports: https
service.beta.kubernetes.io/aws-load-balancer-type: nlb

为了安全起见,我还在应用程序的服务上启用了ExternalTrafficPolicy: Local,但无济于事。

启用use-proxy-protocol: "true"(可能是因为CloudFlare)。

2021-09-19 12:42:17 
" while reading PROXY protocol, client: x.x.x.x, server: 0.0.0.0:80

如有任何帮助,不胜感激。

Cloudflare支持X-Forwarded-For标头,因此您可以尝试配置:

config:
[...]
forwarded-for-header: "X-Forwarded-For"

您似乎能够在设置中正确读取CF-Connecting-IP,因此X-Forwarded-For也应该在来自Cloudflare的请求中可用。

有关更多信息,请参阅支持文章。

最新更新