Microsoft Knowledge Base Email Alertz

FIX: Internet Explorer 6 may unexpectedly close when you try to use digest proxy authentication to connect to secure (HTTPS) Web sites

Search KbAlertz

Advanced Search

Receive Microsoft Knowledge Base articles by E-Mail?

Every night we scan the Microsoft Knowledge Base. If technologies you're interested in are updated, we'll send you an e-mail. You only get one e-mail a day, and only when new articles are added.

Click here to create a
FREE account
Already have an account?
[Click here to Login]











Microsoft Knowledge Base Article

This article contents is Microsoft Copyrighted material.
©2005-©2007 Microsoft Corporation. All rights reserved. Terms of Use | Trademarks

Article ID: 931299 - Last Review: October 8, 2011 - Revision: 3.0

Internet Explorer 6 may close unexpectedly when you try to use digest proxy authentication to connect to HTTPS Web sites

Hotfix download is availableHotfix Download Available
View and request hotfix downloads

On This Page

SYMPTOMS

When you try to use digest proxy authentication to connect to Hypertext Transfer Protocol Secure (HTTPS) Web sites, Microsoft Internet Explorer 6 may close unexpectedly. This problem occurs when Internet Explorer connects to HTTPS Web sites by using the Microsoft Windows Internet (WinINet) application programming interface (API) together with digest proxy authentication.

CAUSE

This problem occurs because the Wininet.dll file incorrectly handles HTTP 407 error codes that occur during digest proxy authentication.

RESOLUTION

This problem is fixed in Windows Internet Explorer 7. To obtain Internet Explorer 7, visit the following Microsoft Web site:
http://www.microsoft.com/windows/ie/downloads/default.mspx (http://www.microsoft.com/windows/ie/downloads/default.mspx)

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:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
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 Microsoft Windows XP with Service Pack 1 (SP1), Microsoft Windows XP with Service Pack 2 (SP2), or Microsoft Windows 2000 with Service Pack 4 (SP4).

Restart requirement

You must restart the 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 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 item in Control Panel.
Internet Explorer 6 for Windows Server 2003 SP1
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wininet.dll6.0.3790.2902666,11221-Mar-200705:32x86SP1
Internet Explorer 6 for Windows Server 2003 SP2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wininet.dll6.0.3790.4043670,72021-Mar-200705:37x86SP2
Windows XP SP2 x86 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wininet.dll6.0.2900.2961664,57626-Jul-200612:21x86
Windows 2000 SP4 or Windows XP SP1 x86 version
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Wininet.dll6.00.2800.1504585,21621-Apr-200515:41x86

WORKAROUND

To work around this problem, do not use the HTTPS protocol. You can use a different proxy authentication method. Different proxy authentication methods include NTLM and Kerberos.

STATUS

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

APPLIES TO
  • Microsoft Internet Explorer 6.0, when used with:
    • Microsoft Windows Server 2003 Service Pack 1
Keywords: 
kbautohotfix kbie600fix kbwinxpsp3fix kbwinserv2003presp1fix kbie600sp2fix kbHotfixServer kbqfe kbie600presp2fix kbfix kbbug KB931299
       

Community Feedback System

Very often, it takes hours to solve a problem. Very often, you've looked high and low, and have tried a lot of solutions. When you finally found it, chances are, it was because someone else helped you. Here's your chance to give back. Use our community feedback tool to let others know what worked for you and what didn't.

Please also understand that the community feedback system is not warranted to be correct, it's simply a system that we've built to let people try and help each other. If something in a feedback response doesn't make sense to you, or you're not comfortable making changes that the feedback talks about (like registry edits), please consult a professional.

Thank you for using kbAlertz.com Feedback System.

-- Scott Cate