<mexHttpsBinding>

Article
09/15/2021

Specifies the settings for a binding used for the WS-MetadataExchange (WS-MEX) message exchange over HTTPS.

<configuration>
  <system.serviceModel>
    <bindings>
      <mexHttpsBinding>

Syntax

<mexHttpsBinding>
  <binding closeTimeout="TimeSpan"
            name="string"
            openTimeout="TimeSpan"
            receiveTimeout="TimeSpan"
            sendTimeout="TimeSpan">
  </binding>
</mexHttpsBinding>

Attributes and Elements

The following sections describe attributes, child elements, and parent elements.

Attributes

Attribute	Description
`closeTimeout`	A TimeSpan value that specifies the interval of time provided for a close operation to complete. This value should be greater than or equal to Zero. The default is 00:01:00.
`name`	A string that contains the configuration name of the binding. This value should be unique because it is used as an identification for the binding. Starting with .NET Framework 4, bindings and behaviors are not required to have a name. For more information about default configuration and nameless bindings and behaviors, see Simplified Configuration and Simplified Configuration for WCF Services.
`openTimeout`	A TimeSpan value that specifies the interval of time provided for an open operation to complete. This value should be greater than or equal to Zero. The default is 00:01:00.
`receiveTimeout`	A TimeSpan value that specifies the interval of time provided for a receive operation to complete. This value should be greater than or equal to Zero. The default is 00:10:00.
`sendTimeout`	A TimeSpan value that specifies the interval of time provided for a send operation to complete. This value should be greater than or equal to Zero. The default is 00:01:00.

Child Elements

None.

Parent Elements

Element	Description
<bindings>	This element holds a collection of standard and custom bindings.

Remarks

This binding is essentially a WSHttpBinding binding that supports transport-level security using certificates. For more information about configuring and using such a metadata endpoint, see How to: Configure a Custom WS-Metadata Exchange Binding, How to: Retrieve Metadata Over a non-MEX Binding, and the sample Custom Secure Metadata Endpoint.

Share via