Cannot establish an SSL connection to a server that is running Windows Server 2008 SP2

Applies to: Windows Server 2008 DatacenterWindows Server 2008 EnterpriseWindows Server 2008 for Itanium-Based Systems More

Symptoms


Assume that you set up the Microsoft Application Request Routing (ARR) module for Internet Information Services (IIS) on a Windows Server 2008 Service Pack 2 (SP2)-based computer. Additionally, assume that the ARR module uses Microsoft Windows HTTP Services (WinHTTP) as the proxy client for connecting to remote http servers (for example, JBoss Application servers). In this scenario, the Secure Sockets Layer (SSL) connection to the server fails. Additionally, you receive the following error message:

HTTP 502.3 – bad Gateway
The operation timed out

The WinHTTP functions also return the following error message:

WinHTTP Error 12030/ ERROR_WINHTTP_CONNECTION_ERROR

Cause


This issue occurs because the encrypted header size is not always equal to the unencrypted header size in the SSL connection. 

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 the problem described in this article. 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 website: 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

To apply this hotfix, you must be running Windows Server 2008 Service Pack 2. For more information about how to obtain a Windows Server 2008 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

968849 How to obtain the latest service pack for Windows Server 2008

Registry information

To apply this hotfix, you do not have to make any changes to the registry.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Vista and Windows Server 2008 file information notes
Important Windows Vista hotfixes and Windows Server 2008 hotfixes are included in the same packages. However, only "Windows Vista" is listed on the Hotfix Request page. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows Vista" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
  • The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
    VersionProductSR_LevelService branch
    6.0.600
    2.
    22xxx
    Windows Vista and Windows Server 2008SP2LDR
  • Service Pack 1 is integrated into the release version of Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 and for Windows Vista" section. MUM files and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Winhttp.dll6.0.6002.22870377,34406-Jun-201206:16x86
For all supported x64-based versions of Windows Server 2008 and of Windows Vista
File nameFile versionFile sizeDateTimePlatform
Winhttp.dll6.0.6002.22870442,36806-Jun-201206:22x64
Winhttp.dll6.0.6002.22870377,34406-Jun-201206:16x86
For all supported IA-64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Winhttp.dll6.0.6002.22870961,53606-Jun-201206:12IA-64
Winhttp.dll6.0.6002.22870377,34406-Jun-201206:16x86

Status


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

More Information


For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

For more information about WinHTTP, go to the following Microsoft website:For more information about the WinHTTP error message, go to the following Microsoft website:

Additional file information

Additional file information for Windows Server 2008

Additional files for all supported x86-based versions of Windows Server 2008
File nameX86_5f89d5b5787bc6f89bd70f46d91afb78_31bf3856ad364e35_5.1.6002.22870_none_7042263c0d84de9f.manifest
File versionNot applicable
File size695
Date (UTC)06-Jun-2012
Time (UTC)09:50
PlatformNot applicable
File nameX86_microsoft.windows.winhttp_31bf3856ad364e35_5.1.6002.22870_none_26f26ba9d8a00005.manifest
File versionNot applicable
File size39,288
Date (UTC)06-Jun-2012
Time (UTC)06:32
PlatformNot applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameAmd64_22139a5e3bc653804a991c24a135cbda_31bf3856ad364e35_5.1.6002.22870_none_6bf2c18508ee0081.manifest
File versionNot applicable
File size1,040
Date (UTC)06-Jun-2012
Time (UTC)09:50
PlatformNot applicable
File nameAmd64_microsoft.windows.winhttp_31bf3856ad364e35_5.1.6002.22870_none_8311072d90fd713b.manifest
File versionNot applicable
File size39,318
Date (UTC)06-Jun-2012
Time (UTC)06:35
PlatformNot applicable
File nameWow64_microsoft.windows.winhttp_31bf3856ad364e35_5.1.6002.22870_none_8d65b17fc55e3336.manifest
File versionNot applicable
File size33,017
Date (UTC)06-Jun-2012
Time (UTC)06:21
PlatformNot applicable
Additional files for all supported IA-64-based versions of Windows Server 2008
File nameIa64_78d08ded0996d2650b6ab43b3a169f98_31bf3856ad364e35_5.1.6002.22870_none_9de466abb7c0fc06.manifest
File versionNot applicable
File size1,038
Date (UTC)06-Jun-2012
Time (UTC)09:49
PlatformNot applicable
File nameIa64_microsoft.windows.winhttp_31bf3856ad364e35_5.1.6002.22870_none_26f40f9fd89e0901.manifest
File versionNot applicable
File size39,303
Date (UTC)06-Jun-2012
Time (UTC)06:29
PlatformNot applicable
File nameWow64_microsoft.windows.winhttp_31bf3856ad364e35_5.1.6002.22870_none_8d65b17fc55e3336.manifest
File versionNot applicable
File size33,017
Date (UTC)06-Jun-2012
Time (UTC)06:21
PlatformNot applicable