Forum Discussion
X-Forwarded-For merged into c-ip in the Logs
- Jul 18, 2019
Hi,
I hope the following links helps.
Regards.
https://support.f5.com/csp/article/K4816
https://devcentral.f5.com/s/articles/iis-x-forward-for-isapi-filter
Hi,
The first one has content that shows what you need to do to send XFF header to the server.
The other two, may help you a way to read or replace XFF value on c-ip column.
Regards.
My boss shot both ideas down.
Any idea if we can change the column location for the XFF? Maybe have it before or after the Client IP?
- cjuniorJul 19, 2019Nacreous
Hum, the ISAPI option was my choice on past.
Sorry, nothing more on mind at this time.
- cjuniorJul 22, 2019Nacreous
I think the best way is you confirm on your webserver log entries.
Capturing those headers on BIG-IP will just confirm that all was sent.
Regards.
- cjuniorJul 22, 2019Nacreous
If I not wrong, this module replaces the c-ip original value, so, you are able to discard the XFF value on backend. Please, double check it :)
Cheers
- Kyle74Jul 22, 2019Altocumulus
Thank you cjunior, I'm going to try that out, just got the module installed on our 2016 server.
Question though, how would I test to see if this works on a dev server?
- Kyle74Jul 22, 2019Altocumulus
Will do.
Cjunior, with this module installed, should I get rid of my Custom Log that has X-Forwarded-For set?
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com