Article ID: 814206
This article has been archived. It is offered "as is" and will no longer be updated.
If you call the Server.Transfer method when you install a custom HTTP filter for an ASP.NET application, the call does not generate output from the Web page to the location that you specified.
This problem occurs because an internal call to the Response.End method skips the execution step of the filter when the output goes through the process pipeline.
If you do not install custom HTTP filters, the Server.Transfer method behaves as expected.
A supported hotfix 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 hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft .NET Framework service pack that contains this hotfix.
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:
http://support.microsoft.com/contactus/?ws=supportNote 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.
The English version of this hotfix 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 -------------------------------------------------------------- 06-Feb-2003 01:18 1.0.3705.400 196,608 Aspnet_isapi.dll 06-Feb-2003 01:13 20,342 Aspnet_perf2.ini 06-Feb-2003 01:13 4,169 Aspnet_perf.h 06-Feb-2003 01:13 20,468 Aspnet_perf.ini 06-Feb-2003 01:18 1.0.3705.400 24,576 Aspnet_regiis.exe 06-Feb-2003 01:18 1.0.3705.400 28,672 Aspnet_wp.exe 05-Feb-2003 23:00 1.0.3705.400 69,632 Corperfmonext.dll 05-Feb-2003 22:59 1.0.3705.400 303,104 Mscorjit.dll 06-Feb-2003 12:20 1.0.3705.400 1,953,792 Mscorlib.dll 05-Feb-2003 23:00 1.0.3705.400 2,269,184 Mscorsvr.dll 01-Aug-2002 20:38 15 Smartnav.htm 17-Oct-2002 16:55 8,728 Smartnav.js 05-Feb-2003 22:59 1.0.3705.400 2,269,184 Mscorwks.dll 06-Feb-2003 12:24 1.0.3705.400 1,191,936 System.web.dll
If you applied the hotfix in this article for Microsoft ASP.NET included with the .NET Framework 1.0, and if you upgraded to Microsoft ASP.NET included with the .NET Framework 1.1, apply the hotfix package from the following Microsoft Knowledge Base article:
821156Additionally, if you upgraded to the .NET Framework 1.1, and if you experience the symptoms in this article, apply the hotfix package from Knowledge Base article 821156.
(http://support.microsoft.com/kb/821156/ )INFO: ASP.NET 1.1 June 2003 Hotfix Rollup Package
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.