BUG: SOAP Toolkit 2.0 Client Does Not Respond When it Makes a Secure Sockets Layer Connection to a Port Other than to Port 443 (811987)


The information in this article applies to:

  • Microsoft SOAP Toolkit 2.0, when used with:
    • the operating system: Microsoft Windows NT 4.0 SP6a
    • the operating system: Microsoft Windows 2000

SYMPTOMS

When a Microsoft SOAP client that is implemented with the SOAP Toolkit 2.0 tries to make a Secure Sockets Layer (SSL) connection to communicate with a secure SOAP Service on a port other than the default SSL port 443, the SOAP client does not respond. You receive the following error message:
C++ HRESULT: 0x800A151E, HTTP_CONNECTION_FAILED
VB Error: Run-time error '5406': Application defined or object defined error.
If you use the high-level API in this scenario, the SoapClient object has the following Detail property:
Client:Sending the Soap message failed or no recognizable response was received HRESULT=0x800A151E - Client:Connection failed.
HRESULT=0x800A151E

CAUSE

The SOAP Toolkit 2.0 HttpConnector implementation on Microsoft Windows 2000 and Microsoft Windows NT 4.0 ignores the port information that an https URL provides. The HttpConnector implementation always tries to make the SSL connection on the default SSL port 443.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.

REFERENCES

For more information about SOAP Toolkit 2.0 and security, visit the following Microsoft Developer Network Web site and read the white paper, Building Secure Web Services with Microsoft SOAP Toolkit 2.0:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsrvspec/html/soapsecurity.asp

Modification Type:MajorLast Reviewed:6/5/2003
Keywords:kbpending kbBug KB811987
©2002 Microsoft Corporation. All rights reserved.