Represents a collection of configuration elements that specify pass through filters, which provide a mechanism to pick the appropriate Internet Information Services (IIS) bindings when hosting the Windows Communication Foundation (WCF) application in IIS.
<baseAddressPrefixFilters> does not recognize “localhost”, use the fully qualified machine name instead.
<serviceHostingEnvironment> <baseAddressPrefixFilters> <add prefix="string"/> </baseAddressPrefixFilters> </serviceHostingEnvironment>
The following sections describe attributes, child elements, and parent elements.
|<add>||Adds a configuration element that specifies a prefix filter for the base addresses used by the service host.|
|<serviceHostingEnvironment>||Defines the type the service hosting environment instantiates for a particular transport.|
A prefix filter provides a way for shared hosting providers to specify which URIs are to be used by the service. It enables shared hosts to host multiple applications with different base addresses for the same scheme on the same site.
IIS Web sites are containers for virtual applications which contain virtual directories. The application in a site can be accessed through one or more IIS bindings. IIS bindings provide two pieces of information: binding protocol and binding information. Binding protocol (for example, HTTP) defines the scheme over which communication occurs, and binding information (for example, IP Address, Port, Hostheader) contains data used to access the site.
IIS supports specifying multiple IIS bindings for each site, which results in multiple base addresses for each scheme. Because a WCF service hosted under a site allows binding to only one base address for each scheme, you can use the prefix filter feature to pick the required base address of the hosted service. The incoming base addresses, supplied by IIS, are filtered based on the optional prefix list filter.
For example, your site can contain the following base addresses.
You can use the following configuration file to specify a prefix filter at the appdomain level.
<system.serviceModel> <serviceHostingEnvironment> <baseAddressPrefixFilters> <add prefix=”net.tcp://test1.fabrikam.com:8000”/> <add prefix=”http://test2.fabrikam.com:9000”/> </baseAddressPrefixFilters> </serviceHostingEnvironment> </system.serviceModel>
In this example,
http://test2.fabrikam.com:9000 are the only base addresses for their respective schemes, which are allowed to be passed through.
By default, when prefix is not specified, all addresses are passed through. Specifying the prefix only allows the matching base address for that scheme to be passed through.
The filter does not support any wildcards. In addition, the baseAddresses supplied by IIS may have addresses bound to other schemes not present in the