A recent customer issue came up where they were load balancing servers but we unable to get the true client address logged in their IIS logs. They had their servers fronted by a BIG-IP and when clients would make requests the address passed to the server was the internal address and not that of the client.
This is a common issue with proxies and fortunately there is a standard for forwarding client information. It is the HTTPX-Forwarded-For header which is handled by most proxies. So, I set out to find an existing ISAPI filter to replace the c-ip (client ip) log value in IIS with the contents of the X-Forwarded-For header (if it exists). I was amazed to find that I couldn’t find a single instance of any open source (or even commercial) filter that would do this.
So, I dug out Visual Studio and whipped up a filter that does just that. It’s very basic and contains no user configuration so all you need to do is plug it into your Web Applications list of ISAPI Filters within the IIS Administration and you’re set to go.
We’ve released the source under the iControl End User License Agreement (available in any iControl SDK download). You can download it here. If you find a way to optimize this filter, please let me know and I’ll update the sources here.
After 24-hours of posting, a customer already returned some performance testing on the filter indicating that it only effected the traffic by less than 1 percent. I’m sure there are ways to optimize the memory allocation in the filter to speed this up a bit more, but I’ll leave that for the community to work on.
Oh, and it should be noted that the X-Forwarded-For header isn’t supported the same way across all proxy products so you’ll want to make sure you test this out before using it. It is expecting the header to only contain an IP Address as it does a straight substitution on the value in the c-ip section of the log entry.
Currently the code does a straight replacement IF the X-Forwarded-For header exists.
I guess I’m not clear on why internal networks are different than external ones. In your case doesn’t the internal proxy add the X-Forwarded-For header with the true client address? If so, then this filter will replace the address.
The real problem is that the proxy is hiding the original source address and throwing in it’s own. So there is no way for the filter to know what the true address is unless the proxy is passing it through directly. In which case you don’t need the X-Forwarded-For header. Am I missing something?
I’d be glad to make modifications to the filter if it makes sense to a wide audience. The C++ code is very simple…
Good points - I’m sold. I’ll incorporate the check for internal networks and bypass replacement of the X-Forwarded-For header if the source address is from the ranges specified above.
Since I can’t really test this on my setup, if anyone is willing to test out my code changes, I’ll be able to post them for everyone to share.
Oh, and I’ve made a few more optimizations in the code for the cases when X-Forwarded-For headers aren’t passed in.
The only thing I really need from you is your contact information? You can send it to me privately by clicking on the “Contact Me” link on the top left of my blog. Then I can get you the updated filter.
If the status is Unknown, that means that you haven’t sent any traffic through it. Try accessing one of the pages on that website and the status will either be an up arrow (good) or a red arrow (bad) but shouldn’t be Unknown.
Also, I don’t believe you need to create a new application. All I did was to add it to the filters list within an existing website.
Glad you like it! As far as I know there is no way to add headers to the IIS log facility. So, this filter will replace the C-IP value with the contents of the X-Forwarded-For header (if it exists).
Not sure what’s different with a SSL configured server. As far as I’m aware, the SSL decryption is performed before the content gets to the ISAPI filters. I see no reason why one would work and the other wouldn’t.
It’s nothing that complicated. All it does is read the X-Forwarded-For HTTP header sent to the webserver from the firewall (or other intermediary) and replaces the c-ip field in the IIS logs with that value for that request. Otherwise, there is no other way with IIS to show the true identity of a client if a firewall changes the source ip address.
Thanks for the link Mike. I believe the code in that blog post is very similar to my filter. I’ve also got support for an ini-file override of the header name.
I think I’ve got David’s post by 5 days though B-).
This filter does not do anything with the headers. It looks for a header (X-Forwarded-For by default, but overridable by a ini file). If that header is found, it replaces the contents of the IIS C-IP value with the contents of that header.
It does not add or remove headers so any HTTP header that is passed into it, will be passed on to the web application. There is no rewriting needed as this is just a filter. It just sniffs whats coming in and passes it through to the backend.
So, if a X-Forwarded-For header is passed it to the filter, it will be passed out as well. Are you seeing different behvavior? The source is available for download as well if you want to look for yourself at what the filter does.
Any known issues for this filter related to IIS 6? I can’t get the filter to load in IIS 6 worker process isolation mode. IIS 5 compatibility mode seems to work fine. Thanks!!
Right now, all it does is look for an incoming X-Forwarded-For HTTP header. If it’s found, the value in it is used for the c-ip value in the IIS access logs. I’m sure you could write a filter that does what you propose, or take the source from the XFF filter and tailor it to your needs, but this one doesn’t do what you are asking.
Great, Glad it helped you out. The HTTP profile will be the best performing option but there are cases where you may want to do this conditionally. If so, then you’re best bet is in an iRule.
