Article ID: 916833 - Last Review: December 3, 2007 - Revision: 2.3 FIX: The contents of the Request.ClientCertificate("Certificate") field are incorrect when an .asp Web page is hosted on IIS 6.0On This PageSYMPTOMSConsider the following scenario. You browse an .asp Web page that is hosted on Microsoft Internet Information Services (IIS) 5.0. You then use the same client and keyset to browse the same .asp Web page, but the Web page is hosted on IIS 6.0. In this scenario, the contents of the Request.ClientCertificate("Certificate") field are incorrect when the page is hosted on IIS 6.0. For example, the last byte of the content is incorrect when you use a COM component to write the content to a certificate in ASN.1 format. CAUSEThis issue occurs because the size and offset of the certificate content are not calculated correctly when the .asp Web page is hosted on IIS 6.0. RESOLUTIONService pack informationTo resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:889100
(http://support.microsoft.com/kb/889100/
)
How to obtain the latest service pack for Windows Server 2003 Hotfix informationPrerequisitesYou must have Windows Server 2003 Service Pack 1 installed to apply this hotfix.Restart requirementYou do not have to restart the computer after you apply this hotfix.Hotfix replacement informationThis hotfix does not replace any other hotfixes.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.Microsoft Windows Server 2003, ia-64 Collapse this table
Collapse this table
Collapse this table
WORKAROUNDTo work around this issue, convert the .asp page to Microsoft ASP.NET. STATUSMicrosoft 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 Windows Server 2003 Service Pack 2.
| Article Translations
|
Back to the top
