Server.Transfer( *url*) ?
(HttpServerUtility method)
I know almost nothing about ASP.NET, but from my Java web developer, redirection is bad because it includes a different round-trip network to the browser and back when you really want to continue processing on another page.
And Response.Redirect () does indeed return a 302 response code ("try a different URL") back to the browser. Ugh. XP
Server.Transfer () looks like a java version of Response.Forward ()
Johnl4
source share