FIX: Predefined WCF Bindings not taking in account a default Web proxy configuration in BizTalk Server

Symptoms

When predefined WCF bindings such as basicHttpBinding, webHttpbinding, and WSHttpBinding are used, the default proxy configuration in Microsoft Internet Explorer settings or in <defaultProxy> of a Microsoft BizTalk Server configuration file are ignored and not used.

Resolution

This problem is fixed in the following cumulative updates for BizTalk Server:

More information

The default proxy is used if the send port is set to "Use proxy" and the proxy address is not provided in the send port transport properties. If "Use send handler proxy settings" is selected, send port uses the same proxy settings as the send handler that hosts this port.
 

System proxy credentials can be provided from Windows Credential Manager by creating a new generic credential. If there is no generic credential for the corresponding proxy server, the Windows credentials of the context user are used for authentication.

References

For more information about the service packs and cumulative update list for BizTalk Server, see the following article in the Microsoft Knowledge Base:

2555976 Service pack and cumulative update list for BizTalk Server

For more information about BizTalk Server hotfixes, see the following article in the Microsoft Knowledge Base:

2003097 Information about BizTalk hotfixes and Cumulative Update support

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.

×