-
Notifications
You must be signed in to change notification settings - Fork 38.8k
Description
We have updated Spring framework to 5.2.9.RELEASE (from 5.1.5.RELEASE) and Sprint boot to 2.3.4.RELEASE (from 2.1.4.RELEASE).
We use X-Forwarded-For for Security Audit logging of the Source IP (Client's IP).
Now we are no longer able to access X-Forwarded-For header and this functionality seems to be broken.
Previous Version:
x-forwarded-for 10.206.135.122, 10.91.122.122
x-forwarded-proto http
x-forwarded-host cp0704.x.y.z.net
x-forwarded-port 8000
x-real-ip 10.91.122.122
content-length 384
x-request-id 9c7d4d3b35705dd905899f13adf973a8
x-original-uri /a/b/c/d?Override=true
x-scheme https
content-type application/json
user-agent PostmanRuntime/7.26.8
accept /
cache-control no-cache
postman-token ffbe2fa4-90f9-4ac5-bd2f-8853c33135c5
accept-encoding gzip, deflate, br
After Upgrade:
x-forwarded-proto http
x-forwarded-host cp0704.x.y.z.net
x-forwarded-port 8000
x-real-ip 10.91.122.122
content-length 384
x-request-id 6024ea0cf66249ad03b3cb33868c94a0
x-original-uri /a/b/c/d?Override=true
x-scheme https
content-type application/json
user-agent PostmanRuntime/7.26.8
accept /
cache-control no-cache
postman-token a8e82716-cdc1-4fb6-b0fc-8839eb72eb29