
Explanation/Reference:
Explanation:
Target 1: mexHttpBinding
Target 2: IMetadataExchange
Example of valid endpoint definition for the MEX protocol:
<endpoint address="mex"
binding="mexHttpBinding"
contract="IMetadataExchange"/>
Target 3: httpGetEnabled
Target 4: true
Cervice behaviors are configured for the default endpoints by using anonymous <behavior> sections within
<serviceBehaviors> sections. Any unnamed <behavior> elements within <serviceBehaviors> are used to configure service behaviors. For example, the following configuration file enables service metadata publishing for all services within the host.
<system.serviceModel>
<behaviors>
<serviceBehaviors>
<behavior>
<serviceMetadata httpGetEnabled="True"/>
</behavior>
</serviceBehaviors>
</behaviors> <!-- No <service> tag is necessary. Default endpoints are added to the service -->
<!-- The service behavior with name="" is picked up by the service -->
</system.serviceModel>
References: https://docs.microsoft.com/en-us/dotnet/framework/wcf/simplified-configuration
Recent Comments (The most recent comments are at the top.)
should be false
Must be false