Availability of Microsoft Windows HTTP Services 5.0 Rollup2 hotfix (813793)


The information in this article applies to:

  • Microsoft Windows HTTP Services (WinHTTP) 5.0, when used with:
    • the operating system: Microsoft Windows 2000 (Service Pack 3)
    • the operating system: Microsoft Windows NT 4.0 SP6a

SYMPTOMS

The Microsoft Windows HTTP Services 5.0 Rollup2 fix corrects the problems that are described in the following Microsoft Knowledge Base articles:

323035 FIX: SetClientCertificate may not select the correct client certificate

323376 FIX: WinHttpRequest sends a "Content-Length: 0" header for GET requests

323379 FIX: Chunked encoding processing breaks with more than one trailing header

This rollup also contains a fix for an access violation that may generate the following call stack:
ChildEBP RetAddr Args to Child 
0012f93c 64c03526 00040000 00000000 00000028 WINHTTP5!ICSecureSocket::MatchSecureProtocolSemantics+0x3 
0012f96c 64c061f3 00040000 00001f90 00000000 WINHTTP5!CServerInfo::FindKeepAliveConnection+0x73 
0012f9ac 64c06108 00000000 01362000 01366320 WINHTTP5!CServerInfo::GetConnection_Fsm+0x11e 
0012f9bc 64c01db3 01366320 00040000 00000000 WINHTTP5!CFsm_GetConnection::RunSM+0x46 
0012f9d4 64c01d7f 01362000 00000000 00000000 WINHTTP5!CFsm::Run+0x1e 
0012f9f4 64c06022 01366320 01362000 01366280 WINHTTP5!DoFsm+0x26 
0012fa2c 64c05ed6 01366280 64c01db3 01366280 WINHTTP5!HTTP_REQUEST_HANDLE_OBJECT::OpenConnection_Fsm+0x189 
0012fa34 64c01db3 01366280 00000000 00000000 WINHTTP5!CFsm_OpenConnection::RunSM+0x33 
0012fa4c 64c01d7f 01362000 00000000 00000000 WINHTTP5!CFsm::Run+0x1e 
0012fa6c 64c05e7a 01366280 01390000 64c05e19 WINHTTP5!DoFsm+0x26 
0012fa78 64c05e19 00000000 00000000 01362000 WINHTTP5!HTTP_REQUEST_HANDLE_OBJECT::OpenConnection+0x2c 
0012faa0 64c05d8b 013661e0 64c01db3 013661e0 WINHTTP5!HTTP_REQUEST_HANDLE_OBJECT::MakeConnection_Fsm+0x95 
0012faa8 64c01db3 013661e0 01390000 00000000 WINHTTP5!CFsm_MakeConnection::RunSM+0x33 
0012fac0 64c01d7f 01362000 00000000 00000000 WINHTTP5!CFsm::Run+0x1e 
0012fae0 64c03b9a 013661e0 01362000 01366140 WINHTTP5!DoFsm+0x26 
0012fb10 64c03b2a 00000000 64c01db3 01366140 WINHTTP5!HTTP_REQUEST_HANDLE_OBJECT::SendRequest_Fsm+0x81 
0012fb18 64c01db3 01366140 01390000 00000000 WINHTTP5!CFsm_SendRequest::RunSM+0x33 
0012fb30 64c01d7f 01362000 00000000 00000000 WINHTTP5!CFsm::Run+0x1e 
0012fb50 64c0417c 01366140 01362000 013641c0 WINHTTP5!DoFsm+0x26 
0012fb70 64c04056 00000000 64c01db3 013641c0 WINHTTP5!HTTP_REQUEST_HANDLE_OBJECT::HttpSendRequest_Start+0x27d 
0012fb78 64c01db3 013641c0 77e86ac3 00000000 WINHTTP5!CFsm_HttpSendRequest::RunSM+0x48 
0012fb90 64c069bc 01362000 00000000 00000000 WINHTTP5!CFsm::Run+0x1e
0012fbdc 64c0a5ef 013641c0 01390364 00000000 WINHTTP5!StartFsmChain+0xcb 
0012fc20 64c0a4a2 01390000 00000000 00000000 WINHTTP5!HttpWrapSendRequest+0x18f 
0012fc74 64c0c3db 01390000 00000000 00000000 WINHTTP5!WinHttpSendRequest+0x18f 
0012fcc0 69bc320e 01364000 cccc000a cccccccc WINHTTP5!CHttpRequest::Send+0x146 
0012fcfc 69bc2264 0012fce8 cccc0008 cccccccc msxml4!CServerXMLHTTP::send+0x15f
This symptom may occur if either of the following conditions exist:
  • An HTTPS request is going through a proxy that requires NTLM authentication, and the default credentials do not have access. The HTTP request is going through the same proxy again.
  • An HTTPS request is going through a proxy that requires NTLM authentication, the default credentials do have access, the initial HTTP 407 response from the proxy contains data content (Content-Length is not 0), and the initial HTTP 407 response does not contain a "Proxy-Connection: Close" header. The HTTP request is going through the same proxy again.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft Windows XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

322389 How to obtain the latest Windows XP service pack

Rollup information

A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/default.aspx?scid=fh;EN-US;CNTACTMS

Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

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
   --------------------------------------------------------
   31-Jan-2003  14:33  5.0.2613.1002  289,792  Winhttp5.dll

WORKAROUND

To work around this problem, use a Proxy Server that does not require Integrated Windows Authentication.

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Microsoft Windows XP Service Pack 2.
Modification Type:MinorLast Reviewed:10/13/2005
Keywords:kbHotfixServer kbQFE kbWinXPsp2fix kbQFE kbWinXPpreSP2fix kbfix kbbug KB813793
©2004 Microsoft Corporation. All rights reserved.