Forum Discussion
KaiTT
Nimbostratus
NimbostratusHTTP x-forward-for
Hi all, I have configured the x-forward-for virtual server as below. <vitual server> type : standard protocol : tcp Source Address Translation : Automap HTTP Profile : Added profile with 'In...
zamroni777
Nacreous
Nacreousthe vserver port number should not matter.
do tcpdump on the vserver for both scenarios then check the http headers.
if your vserver is ssl terminating, add ssl decrypt option
https://clouddocs.f5.com/training/community/adc/html/class4/module1/lab10.html
in your situation, i suspect there is node between client and f5 that actually fills the the xff header.
KaiTTThe capture below is the result of configuring XXF with 11211 ports.
Because BIG-IP recognizes 11211 port as TCP, it appears that HTTP headers cannot be added.