X-Forwarded-For header is being passed

[rubenstolk]

Maybe something changed in AWS infrastructure, but while creating an entry like this:

fire.py --command create --url https://ifconfig.me/ --region eu-west-1 --access_key ABC --secret_access_key "XYZ"

I do see my IP in the X-Forwarded-For response on the ifconfig.me page.

[Nagaev]

You can use the X-My-X-Forwarded-For header to replace your origin IP in X-Forwarded-For

[Exla]

Is there any update on this? I still see the original IP in the X-Forwarded-For header, even when using X-My-X-Forwarded-For

connect to [XXX] from (UNKNOWN) [XXX]
GET / HTTP/1.1
accept: */*
User-Agent: curl/8.9.1
X-Amzn-Trace-Id: Root=XXX
X-Forwarded-For: XXX
X-Forwarded-Port: 443
X-Forwarded-Proto: https
x-my-x-forwarded-for: 1.2.3.4
x-amzn-apigateway-api-id: XXX
Host: XXX