WCF 4.0 has solved this issue in some instances with a new config option that use Request Headers:
<behaviors>
<serviceBehaviors>
<behaviorname="XXXXXXX">
<useRequestHeadersForMetadataAddress/>
</serviceBehaviors>
</behaviors>
WCF 4.0 has solved this issue in some instances with a new config option that use Request Headers:
<behaviors>
<serviceBehaviors>
<behaviorname="XXXXXXX">
<useRequestHeadersForMetadataAddress/>
</serviceBehaviors>
</behaviors>