Article ID: 834270 - View products that this article applies to.
For a Microsoft .NET Framework 1.0 version of this article, see 829930
You can configure an HTTP handler to handle all file name extensions that have no mappings. If the handler is configured this way, and you visit a Web site in a virtual directory that contains an application that has no mappings for a specific file name extension, the handler can write a response or redirect your browser as necessary.
However, if you visit a Web site in a virtual directory that contains an application that has no mappings for a specific file name extension, you may receive an "HTTP 404 Error" error message instead.
This problem may occur if you visit a URL for a default file that is located in a subfolder that does not exist in the virtual directory that is mapped to the handler.
The first time that your browser requests the URL, the handler responds as expected. If you try to visit a specific .aspx page in the same non-existent folder, you receive an "HTTP 404 Error" error message. This is also the expected behavior.
However, if you try to request the original URL that the handler responded to, regardless of whether you reload the page, you receive an "HTTP 404 Error" error message for that request instead of the response from the handler that you received on the first visit. The handler will not run again until Microsoft ASP.NET is recycled.
Important This software update contains two types of packages: a Microsoft Windows Installer (.msi) package, and an Optional Component Manager (OCM) package. If you use Microsoft Windows Server 2003, you must specify that you require the Windows Server 2003 (OCM) update because Windows Server 2003 File Protection monitors the Microsoft .NET Framework 1.1 files. If you use an operating system that is different from Windows Server 2003, you must continue to use the Windows Installer package.
Software update informationA supported software update is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This software update may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next .NET Framework 1.1 service pack that contains this software update.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the software update. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMSNote 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.
PrerequisitesNo prerequisites are required.
Restart requirementYou may have to restart your computer if any services or applications that use files that appear in the "File information" section of this article are running when you apply this software update.
Software update replacement informationThis software update does not replace any other software updates.
File informationThe English version of this software update has the file attributes (or later) 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.
Date Time Version Size File name --------------------------------------------------------------------------------------------- 30-Jan-2004 04:16 1.1.4322.995 258,048 Aspnet_isapi.dll 30-Jan-2004 04:16 1.1.4322.995 20,480 Aspnet_regiis.exe 30-Jan-2004 04:16 1.1.4322.995 32,768 Aspnet_state.exe 30-Jan-2004 04:16 1.1.4322.995 32,768 Aspnet_wp.exe 16-May-2003 00:49 33,522 Installpersistsqlstate.sql 16-May-2003 00:49 34,150 Installsqlstate.sql 30-Jan-2004 04:06 1.1.4322.995 94,208 Perfcounter.dll 30-Jan-2004 04:11 8,571 Smartnav.js 30-Jan-2004 17:14 1.1.4322.995 1,220,608 System.dll 30-Jan-2004 17:14 1.1.4322.995 241,664 System.messaging.dll 30-Jan-2004 17:15 1.1.4322.995 323,584 System.runtime.remoting.dll 30-Jan-2004 17:14 1.1.4322.995 131,072 System.runtime.serialization.formatters.soap.dll 30-Jan-2004 17:15 1.1.4322.995 1,257,472 System.web.dll 30-Jan-2004 17:14 1.1.4322.995 819,200 System.web.mobile.dll 30-Jan-2004 17:14 1.1.4322.995 569,344 System.web.services.dll 30-Jan-2004 17:14 1.1.4322.995 1,339,392 System.xml.dll 30-Jan-2004 04:11 14,482 Webuivalidation.js
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Steps to reproduce the behavior
Code for HandlerError.cs
For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/307985/ )INFO: ASP.NET HTTP modules and HTTP handlers overview
(http://support.microsoft.com/kb/308001/ )HOW TO: Create an ASP.NET HTTP handler by using Visual C# .NET
(http://support.microsoft.com/kb/307997/ )HOW TO: Create an ASP.NET HTTP handler by using Visual Basic .NET
Article ID: 834270 - Last Review: April 7, 2006 - Revision: 2.2