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.

Applications that use the WinINet API may not respond to a server as expected when you use Internet Explorer 6


View products that this article applies to.

Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 (http://support.microsoft.com/kb/256986/ ) Description of the Microsoft Windows Registry

↑ Back to the top


Symptoms

In Microsoft Internet Explorer 6, when an application uses the Windows Internet (WinINet) API to query the status of a response from a server, the application may not respond to the server as expected.

↑ Back to the top


Cause

This problem may occur if the first response that the server sends is "100 Continue." A server sends a "100 Continue" response to indicate that the rest of the request can be sent. The "100 Continue" response is not the server's final response.

However, WinINet sends to the application the first response that it receives from the server. If the server sends a "100 Continue" response, WinINet treats that response as the server's final response and sends the response to the application. The application does not receive the server's next response and therefore cannot respond to the server as expected.

↑ 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.

Registry information

After you apply this hotfix, you must change the registry to add the required subkey, entry, and value. To do this, follow these steps.Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
  1. Click Start, click Run, type regedit, and then click OK.
  2. Expand the following subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl
  3. Right-click FeatureControl, point to New, and then click Key.
  4. Type FEATURE_HANDLE_HTTP_STATUS_CONTINUE_KB8902150, and then press ENTER to name the new subkey.
  5. Right-click FEATURE_HANDLE_HTTP_STATUS_CONTINUE_KB8902150, point to New, and then click String Value.
  6. Type iexplore.exe, and then press ENTER to name the new value.
  7. Double-click iexplore.exe.
  8. In the Value data box, type 1, and then click OK.
  9. Quit Registry Editor.

File information

The English version of this hotfix has the file attributes (or later file attributes) 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.
Internet Explorer 6 for Microsoft Windows NT 4.0 with Service Pack 6a, Windows 98, and Windows Millennium Edition
   Date         Time   Version           Size     File name
   --------------------------------------------------------------
   03-Mar-2003  17:24  6.0.2800.1172      33,792  Ieuninst.exe     
   01-Oct-2004  07:36  6.0.2800.1473      30,208  Ieupdate.exe     
   03-Dec-2004  01:56  6.0.2800.1482     581,120  Wininet.dll

				
Internet Explorer 6 for Microsoft Windows 2000 and Windows XP
   Date         Time   Version           Size     File name
   --------------------------------------------------------------
   21-Sep-2004  03:21  6.0.2800.1473      38,912  Iecustom.dll     
   03-Dec-2004  01:56  6.0.2800.1482     581,120  Wininet.dll      
   21-Sep-2004  03:21  6.0.2800.1473      38,912  Iecustom.dll

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in Microsoft Internet Explorer 6.

↑ Back to the top


Keywords: KB890215, kbhotfixserver, kbbug, kbfix, kbie600presp2fix, kbie600sp2fix, kbautohotfix

↑ Back to the top

Article Info
Article ID : 890215
Revision : 5
Created on : 8/29/2007
Published on : 8/29/2007
Exists online : False
Views : 342