X-Forwarded-For HTTP Module For IIS7, Source Included!
For those who of you that are having problems with logging client addresses in their server logs because you are running your web servers behind a proxy of some sort, never fear, your solution i...
Published Dec 23, 2009
Version 1.0
RickM
Nimbostratus
Nimbostratus@spellingb We are using it on windows 2016. we've been using it since windows 2008R2.
1 --installing both 64bit and 32bit modules
Put the 64-bit version in c:\program files\f5module. Put the 32-bit version in c:\program files (x86)\f5module.
echo ###loading the module to IIS
c:\windows\system32\inetsrv\appcmd.exe install module /name:F5XFFHttpModule /image:"%%ProgramFiles%%\F5module\F5XFFHttpModule.dll"
using %ProgramFiles% as the folder, whether your IIS app pool is 32-bit or 64-bit, it can get the correct 'bitness' module. The double percent signs %% are needed when this is in a .BAT or .CMD file.
2 -- your bigip *MUST* be inserting the x-forwarded-for header, enabled in the HTTP profile of the vip.
3 -- It only works for successful requests. On HTTP errors for example 404 or 500, it does not get a chance to run so the SNAT address is logged.