- This behavior also occurs when you try to access the forbidden resource by using HTTPS. However, this behavior is by design when you use HTTPS. To view the resource, the client may have to reestablish a new HTTPS connection and re-authenticate to the Web server.
- This behavior only occurs when the Web server returns an HTTP 403 status code. The .NET Framework 2.0 client does not close the persistent connection when the Web server returns other status codes.
- This behavior does not occur when you use the Microsoft .NET Framework 1.1 or earlier versions of the .NET Framework.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: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.
PrerequisitesThe following list contains prerequisites for the hotfix:
- The Microsoft .NET Framework 2.0
Restart requirementYou do not have to restart your computer after you apply this hotfix.
File informationThe 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.
|File name||File version||File size||Date||Time||Platform|
Article ID: 919804 - Last Review: Feb 16, 2017 - Revision: 3