ASP.NET 1.1: FIX: You cannot browse an ASP.NET 1.1 Web site if the User-Agent string that is in the browser contains more than 256 characters

SUPPORT SOLUTION:
You
visit a Microsoft ASP.NET 1.1 Web site
by using a browser that
has a User-Agent string that
contains more than 256 characters. However, you cannot browse the site. Additionally, the layout of the site
is incorrect.This problem occurs because
ASP.NET
1.1 does not recognize the browser
when the User-Agent string
contains more than 256 characters. When
ASP.NET 1.1 does
not recognize the browser,,
the content on the Web
site is
not rendered correctly.Hotfix Information
2, ‘resolution’);
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 the problem described in this article. 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
3, ‘resolution’);
You must have the
Microsoft .NET Framework 1.1 Service Pack 1 (SP1)
installed to apply this hotfix. Restart requirement
3, ‘resolution’);
You must
restart the computer if any of the affected files are being used when you install this
hotfix. You do
not have to restart the computer
if you close all ASP.NET Web sites before you install this hotfix. Hotfix replacement information
3, ‘resolution’);
This hotfix does not replace other hotfixes. File information
3, ‘resolution’);
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.For all supported x86-based versions of the .NET Framework 1.1 SP1
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile
sizeDateTimePlatformAspnet_filter.lib1.1.4322.245624,57609-Sep-200915:22×86Aspnet_isapi.lib1.1.4322.2456258,04809-Sep-200915:22×86Aspnet_wp.exe1.1.4322.245632,76809-Sep-200915:22×86Mscoree.dll2.0.50727.253271,36022-Dec-200612:28×86Mscorees.dll2.0.50727.2536,14422-Dec-200613:02×86Mscorie.dll1.1.4322.245686,01609-Sep-200914:40×86Mscorjit.dll1.1.4322.2456315,39209-Sep-200914:39×86Mscorld.dll1.1.4322.2456102,40009-Sep-200914:40×86Mscorlib.dll1.1.4322.24562,142,20810-Sep-200920:08×86Mscorsn.dll1.1.4322.245677,82409-Sep-200914:40×86Mscorsvr.dll1.1.4322.24562,523,13609-Sep-200914:39×86Mscorwks.dll1.1.4322.24562,514,94409-Sep-200914:40×86Mscorwks.dll1.1.4322.245681,92009-Sep-200914:40×86System.dll1.1.4322.24561,232,89610-Sep-200920:08×86System.web.dll1.1.4322.24561,265,66410-Sep-200920:08×86For all supported x86-based versions of Windows Server 2003 that have the .NET Framework 1.1 SP1 installed
4, ‘resolution’);
Collapse this tableExpand this tableFile nameFile versionFile
sizeDateTimePlatformSP requirementAspnet_filter.dll1.1.4322.245624,57613-Oct-200910:40×86SP2Aspnet_isapi.dll1.1.4322.2456258,04813-Oct-200910:41×86SP2Aspnet_wp.exe1.1.4322.245632,76813-Oct-200910:41×86SP2Netfxupdate.exe1.0.3705.382,98425-Jun-200807:26×86SP2Setregni.exe1.1.4322.203566,60025-Jun-200807:26×86SP2System.web.dll1.1.4322.24561,265,66430-Sep-200904:42×86SP2Togac.exe1.1.4322.225166,60025-Jun-200807:26×86SP2Installation notes
2, ‘resolution’);
Two hotfixes are provided for this problem. Download and apply the
appropriate hotfix for the operating system that your computer is
running.
If your computer is running an x86-based version of Windows
Server 2003, download and install the hotfix that is marked for “the .NET
Framework 1.1 for Windows Server 2003.”If your computer is running another operating system
(this includes x64-based versions of Windows Server 2003 and IA64-based versions of
Windows Server 2003), download and install the hotfix that is marked for “the
.NET Framework 1.1 (MSI install).”Note After you apply the hotfix, ASP.NET
1.1 can recognize User-Agent strings that contain as many as 512 characters. Microsoft
has confirmed that this is a problem in the Microsoft products that are listed
in the “Applies to” section.When you visit a Web site,
your browser sends the User-Agent string to the Web server that hosts the Web
site. The Web server uses the
User-Agent string to provide content that is customized for your browser. To view the User-Agent string of your browser, type
the following text into the address bar: javascript:alert(navigator.userAgent) To view the length of your browser’s User-Agent string, type the
following text into the address bar:javascript:alert(navigator.userAgent.length)For more information about User-Agent strings, visit the
following Microsoft Developer Network (MSDN) Web site: http://msdn.microsoft.com/en-us/library/ms537503(VS.85).aspx
(http://msdn.microsoft.com/en-us/library/ms537503(VS.85).aspx)
To resolve the same problem for ASP.NET 2.0 Web sites, download and apply the hotfix that is described in
the following Microsoft Knowledge Base article:962204 

(http://support.microsoft.com/kb/962204/
)
FIX: You may not successfully browse an ASP.NET Web site if the User-Agent string contains more than 256 characters

For File Repair and Data Recovery, visit File Repair / Data Recovery