Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

A Client Certificate on One Request Handle May Interfere with Secure Sockets Layer (SSL) Negotiations on Other Request Handles When You Use WinHTTP


View products that this article applies to.

Symptoms

When you use Microsoft Windows HTTP Services (WinHTTP), setting a client certificate on one request handle may interfere with Secure Sockets Layer (SSL) negotiations on other request handles that are sent to the same host or to the same port. As a result, if Microsoft SharePoint Portal Server is installed on the server, the Microsoft SharePointPS Search service does not crawl certain pages of the portal site that use a client certificate.

↑ Back to the top


Cause

This issue occurs because, in a session, WinHTTP incorrectly processes concurrent SSL client authentication negotiation operations that use the same host or the same port.

↑ Back to the top


Resolution

Hotfix Information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

No prerequisites are required.

Restart Requirement

You must restart your computer after you apply this hotfix.

Hotfix Replacement Information

This hotfix does not replace any other hotfixes.

File Information

The English version of this hotfix has the file attributes (or later) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Date         Time   Version      Size     File name
-----------------------------------------------------
19-Aug-2003  21:46  5.2.3790.68  336,384  Winhttp.dll

↑ Back to the top


Workaround

To work around this problem, do one of the following, as appropriate to your situation:
  • Open a different session for each virtual directory on the server that requires a client certificate.

    -or-
  • Serialize the SetOption(CERT_CONTEXT) call in a session, and do not call WinHTTP when either a SendRequest or a ReceiveResponse call is in progress in the session.

↑ Back to the top


Status

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

↑ Back to the top


Keywords: KB826240, kbwinserv2003presp1fix, kbqfe, kbfix, kbbug, kbqfe, kbhotfixserver, kbautohotfix

↑ Back to the top

Article Info
Article ID : 826240
Revision : 18
Created on : 7/24/2007
Published on : 7/24/2007
Exists online : False
Views : 291