Export (0) Print
Expand All

HttpServerUtility.Transfer Method (IHttpHandler, Boolean)

Terminates execution of the current page and starts execution of a new request by using a custom HTTP handler that implements the IHttpHandler interface and specifies whether to clear the QueryString and Form collections.

Namespace: System.Web
Assembly: System.Web (in system.web.dll)

'Declaration
Public Sub Transfer ( _
	handler As IHttpHandler, _
	preserveForm As Boolean _
)
'Usage
Dim instance As HttpServerUtility
Dim handler As IHttpHandler
Dim preserveForm As Boolean

instance.Transfer(handler, preserveForm)
public void Transfer (
	IHttpHandler handler, 
	boolean preserveForm
)
public function Transfer (
	handler : IHttpHandler, 
	preserveForm : boolean
)
Not applicable.

Parameters

handler

The HTTP handler that implements the IHttpHandler to transfer the current request to.

preserveForm

true to preserve the QueryString and Form collections; false to clear the QueryString and Form collections.

Exception typeCondition

ApplicationException

The current page request is a callback.

You can write custom HTTP handlers to process specific, predefined types of HTTP requests in any language that is compliant with the Common Language Specification (CLS). Executable code that is defined in the HTTP handler classes instead of conventional ASP (also known as classic ASP) pages or ASP.NET pages responds to these specific requests. HTTP handlers allow for interacting with the low-level request and response services of a Web server that is running Internet Information Services (IIS), and they provide functionality that is similar to ISAPI extensions but with a simpler programming model.

If you set preserveForm to true and if the enableViewStateMac attribute of the pages configuration element is true, ASP.NET will raise an exception when the Transfer method is executed because the view state from the page that calls the Transfer method is not valid on the destination page. One of the preserved form fields on the calling page is the hidden __VIEWSTATE form field, which holds the view state for the page. When enableViewStateMac is true, ASP.NET runs a message authentication check on the view state of the destination page when the page is posted back from the client and the check will fail.

For security purposes, you should keep the enableViewStateMac attribute set to true. However, there are other methods available to transfer forms data. For more information, including recommended solutions, see article Q316920, "View State Is Invalid Error Message When You Use Server.Transfer" on the Microsoft Knowledge Base Web site.

ASP.NET does not verify that the current user is authorized to view the resource that is delivered by the Transfer method. Although the ASP.NET authorization and authentication logic runs before the original resource handler is called, ASP.NET directly calls the handler indicated by the Transfer method, and does not rerun authentication and authorization logic for the new resource. If the security policy for your application requires clients to have appropriate authorization to access the resource, the application should force reauthorization or provide a custom access-control mechanism.

You can force reauthorization by using the Redirect method instead of the Transfer method. The Redirect method performs a client-side redirect in which the browser requests the new resource. Because this redirect is a new request entering the system, it is subjected to all the authentication and authorization logic of both the IIS and ASP.NET security policy.

You can verify that the user has permission to view the resource by incorporating a custom authorization method that uses the IsInRole method before the application calls the Transfer method.

Windows 98, Windows Server 2000 SP4, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition

The Microsoft .NET Framework 3.0 is supported on Windows Vista, Microsoft Windows XP SP2, and Windows Server 2003 SP1.

.NET Framework

Supported in: 3.0, 2.0

Community Additions

ADD
Show:
© 2014 Microsoft