The Request object requires two trips to the server and can and will
affect performance.
Generally speaking, since ASP 3.0 and most especially with ASP.NET
the *only* reason to use the Request object to 'redirect' is when you
are redirecting to pages on another server or redirecting to pages that
are *not* .aspx files on the same server from which your code does the
redirection (or .asp files on the same server when using ASP 3.0).
You should be properly informed and as I am taking the responsibility
to do so I am telling you to learn to use the Transfer method when
your business process requires redirection. You also want to learn
the Execute method so you can learn how to return data to the calling
page when redirecting.
Start with MSDN documentation and refine your understanding with
Google searches such as those that follow. For the most part it can be
said that while it is still supported for reasons noted, the Request object
is obsolete.
Google: "transfer method"+"asp.net"
Google: 'execute method"+"asp.net"
--
<%= Clinton Gallagher
A/E/C Consulting, Web Design, e-Commerce Software Development
Wauwatosa, Milwaukee County, Wisconsin USA
NET csgallagher@ REMOVETHISTEXT metromilwaukee.com
URL
http://www.metromilwaukee.com/clintongallagher/
"Paul" <Pa**@discussions.microsoft.com> wrote in message
news:BC**********************************@microsof t.com...
Hi Kevin, got it working, can ignore the prev reply. Thanks for the help.
--
Paul G
Software engineer.
"Kevin Spencer" wrote:
Response.Redirect(Request.QueryString("Redirect"))
--
HTH,
Kevin Spencer
..Net Developer
Microsoft MVP
Big things are made up
of lots of little things.
"Paul" <Pa**@discussions.microsoft.com> wrote in message
news:06**********************************@microsof t.com... Hi Kevin, thanks for the response.
so in the login file what do I pass into the redirect statement as I
normally use it as shown below, with the redirect hardcoded in.
Response.Redirect("denied.htm")
--
Paul G
Software engineer.
"Kevin Spencer" wrote:
> <a
href="http://yourdomain.com/loginpage.aspx?Redirect=someotherpage.aspx"> >
> --
> HTH,
> Kevin Spencer
> ..Net Developer
> Microsoft MVP
> Big things are made up
> of lots of little things.
>
> "Paul" <Pa**@discussions.microsoft.com> wrote in message
> news:CF**********************************@microsof t.com...
> > What I am trying to do is as follows.
> > I have a page with 3 links,that direct the user to 3 different pages
when > selected after login.
> > So all link selections will first direct the user to a login page.
Once > the user logs in then they are directed to the appropriate link.
> > So for all 3 links they all go to a login page, but each link must
pass > information to the login in page, specifically the page to go to after
login > takes place.
> > --
> > Paul G
> > Software engineer.
>
>
>
