x-forwarded-for is not recognized by WebLog Expert

Avatar
jamil haddadin
  • updated
  • Fixed
2015-06-22 23:59:48 10.200.75.20 GET /Style+Library/sama/images/logo.png rev=23 80 - 10.200.4.10 Mozilla/5.0+(Windows+NT+5.1)+AppleWebKit/537.36+(KHTML,+like+Gecko)+Chrome/43.0.2357.130+Safari/537.36 http://www.url.url.url/ar-sa/url/page... 304 0 0 15 105.157.216.251

The system is still taking c-ip as the source IP (10.200.4.10) although i have added a new custom field called 'OriginalIP' which is this one 105.157.216.251
Replies 4
Avatar
0
jamil haddadin
I have already done this using the steps mentioned here:
http://www.iis.net/learn/get-started/...

and i you can see from the log sample attached '105.157.216.251' is the source IP, but it is still not recognizing it, instead it is recognizing '10.200.75.20' which is the private IP.

Let me know if you have an white paper or proper steps for this.

Jamil
Avatar
0
jamil haddadin
Thanks Micheal! updating the name works perfectly :-)
Avatar
1
Michael
IIS 8.5 allows you to specify any field name for the X-Forwarded-For field. The article you metnioned suggests to use the OriginalIP field name. Unfortunately this field name isn't supported by WebLog Expert.

What you need to do is to edit the custom field you created and specify the X-Forwarded-For name for it in the "Field Name" edit box.
Avatar
0
Michael
You need to set the custom field header name to X-Forwarded-For, in this case the problem will recognize the field value as the original visitor IP.

Customer support portal powered by UserEcho