Was this page helpful?
Your feedback about this content is important. Let us know what you think.
Additional feedback?
1500 characters remaining
Collapse the table of content
Expand the table of content


An endpoint can be addressed by one or more SOAP headers in addition to its basic URI. One set of scenarios where this is useful is a set of SOAP intermediary scenarios where an endpoint requires clients of that endpoint to include SOAP headers targeted at intermediaries. This configuration element can be used to define such custom address headers. Entries in the endpoint header collection are user-defined XML elements. Each element has to be well-formed XML.

    <Region xmlns="Uri">"String"</Region>
        <Member xmlns="Uri">"String"</Member>

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



Child Elements


Element Description





Parent Elements


Element Description

<endpoint> of <client>

Configures different types of endpoints.

The optional headers provide more detailed addressing information to identify or interact with the endpoint. For example, headers can indicate how to process an incoming message, where the endpoint should send a reply message, or which instance of a service to use to process an incoming message from a particular user when multiple instances are available.

Build Date:


Community Additions

© 2015 Microsoft