More about Client IP Addresses

Back in May I talked about the problem of getting client IP addresses, which you don't have any good way to solve today in WCF. There were a lot of strong comments on that post that this was a feature that people really needed. As it turns out, this was a feature that we wanted to get into Orcas but couldn't get approval. I took the same questions to TechEd to see what people would say. A lot of customers there really wanted this feature as well.

The good news is that we were able to use all of that feedback to get the feature approved and into the product. When using the TCP and HTTP transports, you'll be able to get a message property off of each message that tells you the IP address and port number of the machine that sent the message. The bad news is that because this was a feature that we did very late, it wasn't done in time to appear in the beta releases. We've actually had this done for a few weeks but people continue to ask for the feature because we've had no way to tell you about it.

Rather than let that continue, we decided to let you know that this was one of the things coming in the final release that you haven't had an opportunity to see yet. Phil Henning is the developer that worked to get this done and he's really wanted to talk about it in the meantime so for those of you that are interested, I'm going to let Phil give you more details about how the message property is used. You should expect to see a post on his blog later today.

Comments

• Anonymous
  September 10, 2007
  AWESOME! Thanks!

• Anonymous
  September 10, 2007
  As Nicholas promised , here is some more information about client IP address in Orcas. In the Orcas release

• Anonymous
  January 23, 2009
  Phil Henning has written about creating a custom username/password validator for HTTP , which is another