As you may recall from my previous post, I recently discovered the situation where WCF gets ticked off (understandably so) when its presented with multiple base-addresses to use from IIS as a result of multiple host headers.  So I thought I had solved my problem, and from my limited testing, it certainly appeared that way.  However, what I failed to properly test was actually *using* both host headers (doh!).  My solution in that post essentially selected one of the host headers and gave that dude the red carpet treatment, essentially ignoring the other.  Bad idea.  The final fix was pretty simple, and can be found in this guy’s article.  The downside to this approach is a hard-coded set of absolute URL’s, but that is livable.  I’m sure we could get fancier with our service host factory and register these endpoint addresses at runtime eliminating this hard-coded aspect, but for me, this is fine for the current project.

FYI, you’ll also see info *in the cloud* regarding the <baseAddressPrefixFilter> configuration section, but from my understanding, that still only assists with selecting *which* base address you want to use, but not if you want *all* the base addresses to work.