Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>According to the <a href="http://msdn.microsoft.com/en-us/library/aa751841.aspx" rel="nofollow">documentation</a> the use of <em>multipleSiteBindingsEnabled</em> tells WCF to ignore any <code>&lt;baseAddressPrefixFilters&gt;</code>.</p> <p><em>"Any baseAddressPrefixFilters settings are ignored, for both HTTP and non-HTTP protocols, when multiple site bindings are enabled using this setting."</em></p> <p>So this configuration contradicts itself, you are specifying address prefixes and simultaneously instructing WCF to ignore them since you are have <em>multipleSiteBindingsEnabled</em> specified.</p> <pre><code>&lt;serviceHostingEnvironment multipleSiteBindingsEnabled="true"&gt; &lt;baseAddressPrefixFilters&gt; &lt;add prefix="net.tcp://log.o1881.no:808/log" /&gt; &lt;add prefix="net.tcp://log.core1.o1881.no:808/log" /&gt; &lt;/baseAddressPrefixFilters&gt; &lt;/serviceHostingEnvironment&gt; </code></pre> <p>I think the <em>multipleSiteBindingsEnabled</em> is best for scenarios where you are only interested in using HTTP schemes.</p> <p>Otherwise don't use it and you can in fact <strong>have multiple tcp.net bindings on different ports in the same IIS Site/App hierarchy</strong>.</p> <pre><code>&lt;serviceHostingEnvironment&gt; &lt;baseAddressPrefixFilters&gt; &lt;add prefix="net.tcp://log.o1881.no:808/log" /&gt; &lt;add prefix="net.tcp://log.core1.o1881.no:808/log" /&gt; &lt;/baseAddressPrefixFilters&gt; &lt;/serviceHostingEnvironment&gt; </code></pre> <p>Hope this helps others :)</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload