This article describes the undocumented change in behavior
of the
HttpServerUtility.Transfer method call from the Microsoft .NET Framework 1.0 to the
Microsoft .NET Framework 1.1.
For more information, visit the
following Microsoft Developer Network (MSDN) Web site:
http://msdn2.microsoft.com/en-us/library/aa332847(VS.71).aspx
(http://msdn2.microsoft.com/en-us/library/aa332847(VS.71).aspx)
The
HttpServerUtility.Transfer method contains two parameters.
- The first parameter is a URL path of the new page on the
server to execute.
- The second optional parameter indicates whether the
Form and the QueryString values can pass from the calling page to the page that the user is
being transferred to.
HttpServerUtility.Transfer(String, Boolean);
In the .NET Framework 1.0, if the second optional parameter of the
HttpServerUtility.Transfer method is not specified, the second parameter is set to
false.
In the .NET Framework 1.1, if the second optional
parameter of the
HttpServerUtility.Transfer method is not specified, the second parameter is set to
true.
The "Parameters" section of the
"HttpServerUtility.Transfer Method (String, Boolean)" topic in MSDN states the
following:
pathThe URL path of the new page on the server to execute.
preserveForm If
true, the
QueryString and
Form collections are preserved. If
false, they are cleared. The default is
false.
The following is the correct information:
pathThe URL path of the new page on the server to execute.
preserveForm If
true, the
QueryString and
Form collections are preserved. If
false, they are cleared. In the .NET Framework 1.0, the default value
of the
preserveForm parameter is
false. In the .NET Framework 1.1, the default value of the
preserveForm parameter is
true.
For more information, visit the following Microsoft
Developer Network (MSDN) Web site: