The complete error message was: “The message with To ‘[my service address]’ cannot be processed at the receiver, due to an AddressFilter mismatch at the EndpointDispatcher.”
We got this message when we deployed our services to the production environment. In this environment we first encounter BIG-IP and clustering. And that’s when we hit this brick wall.
The scenario was that BIG-IP had one DNS-name/Ip-address that “forwarded” request to two different servers. However when we accessed the servers with wsHttpBinding we ran into trouble and the above mentioned error message.
The strange thing was that it worked fine with basicHttpBinding, which puzzled us for a while.
Well, thanks to the excellent knowledge in the Avega Microsoft community, we got an answerer in matter of minutes.
As this post points out you can handle the problem by setting the AddressFilterMode to Any, which basic means - ignore addressfiltering.
As far as I understand WCF matches the address property for the client and the server and if it doesn’t match (according to AddressFilterMode) the above mentioned error message is thrown.
And for the strange behavior that basicHttpBinding worked it must have to do with that basicHttpBinding doesn’t care about that kind of matching. I believe that it has to do with WS-Addressing and that is not a part of basicHttpBinding.
I love to be challenged about this - this is just what we figured out in the project.
Thanks to all that helped us solve this.