Forum Discussion

NewTOF501_15047's avatar
NewTOF501_15047
Icon for Nimbostratus rankNimbostratus
May 15, 2014

X-forwarder is not working

I Enabled the Insert X-Forwarded-For option in the HTTP profile. I am getting null in instead of IP in IBM Http server using following code. LogFormat "%v %{X-Forwarded-For}i %l %u %t \"%r\" %>s %b" ...
Cory_50405's avatar
Cory_50405
Icon for Noctilucent rankNoctilucent
May 15, 2014

Question 1: X-forwarded-for header will work for both HTTP and HTTPS, but you must ensure that you are terminating SSL (using a client SSL profile) on your HTTPS virtual server to give the BIG-IP visibility into the layer 7 data.

 

Question 2: Yes, if you are sniffing the traffic at the server side with something like Fiddler or Wireshark, you should be able to see the client IP address in the X-forwarded-for header field within the capture.

 

  • NewTOF501_15047's avatar
    NewTOF501_15047
    Icon for Nimbostratus rankNimbostratus
    May 15, 2014
    any suggestion why i am not getting X-forward IP
  • Cory_50405's avatar
    Cory_50405
    Icon for Noctilucent rankNoctilucent
    May 15, 2014
    You aren't seeing it in the IBM server log. You need to verify whether the BIG-IP is sending it in the first place to determine whether the issue is with BIG-IP or your server logging mechanism. You can either run a packet capture on the server (Wireshark) or on the BIG-IP (tcpdump).
  • NewTOF501_15047's avatar
    NewTOF501_15047
    Icon for Nimbostratus rankNimbostratus
    May 18, 2014
    i checked request header with fiddler. there is nothing. This vs configure with Source Address Translation = automap