How to set redirect default on login?

[Eric Newton]

Sorry, FormsAuthentication is hard set to "default.aspx" when doing the
RedirectFromLoginPage and/or GetRedirectUrl [which is called by
RedirectFromLoginPage]

Just execute SetAuthCookie and then if Request.QueryString["ReturnUrl"] is
null, then redirect to where you want:

if( [password check passed )
{
FormsAuthentication.SetAuthCookie( [username], [create persistent
cookie] );
string returnUrl = Request.QueryString["ReturnUrl"];
if( returnUrl == null || returnUrl.Length < 1 )
returnUrl = "default.aspx";
Response.Redirect( returnUrl, true );
}
--
Eric Newton
[email]eric@ensoft-software.com[/email]
C#/ASP.net Solutions developer

"Lauchlan M" <LMackinnon@Hotmail.com> wrote in message
news:e4J1zVwZDHA.2960@tk2msftngp13.phx.gbl...

> I want to set the default value for where
>
> FormsAuthentication.RedirectFromLoginPage
>
> sends you if it doesn't have a return value already.
>
> eg after lgin you might wat to send them to /mysecurearea/main.aspx

instead

> of default.aspx.
>
> At the moment it always defaults to default.aspx.
>
> Thanks!
>
> Lauchlan M
>
>

[Lauchlan M]

This is silly design on MS's part IMO.

If I have a page Login.aspx and use
FormsAuthentication.RedirectFromLoginPage it _has_ to go to a default.aspx
in the same directory, and so _cannot_ go to my secure folder. So I end up
with a default.aspx that just redirects to where I really want it to go
which seems like (and is) a cludge.

And what would happen if my login page _was_ default.aspx? Would it just
cycle around to itself on successful login?

Sometimes the .net framework is amazing, sometimes you wonder whether MS
really thought about any of this.

Lauchlan M

> Sorry, FormsAuthentication is hard set to "default.aspx" when doing the
> RedirectFromLoginPage and/or GetRedirectUrl [which is called by
> RedirectFromLoginPage]
>
> Just execute SetAuthCookie and then if Request.QueryString["ReturnUrl"] is
> null, then redirect to where you want:
>
> if( [password check passed )
> {
> FormsAuthentication.SetAuthCookie( [username], [create persistent
> cookie] );
> string returnUrl = Request.QueryString["ReturnUrl"];
> if( returnUrl == null || returnUrl.Length < 1 )
> returnUrl = "default.aspx";
> Response.Redirect( returnUrl, true );
> }

[Eric Newton]

I agree, there are parts of individual classes where some methods are well
written and thought out, and other methods are just silly...

GetRedirectUrl is one of them, it takes two parameters but doesnt even TRULY
use them [it checks the username to see if null and just returns a null if
so]

In my code, if I use GetRedirectUrl You'll frequently see "string url =
FormsAuthentication.GetRedirectUrl("SILLY_BOGUS_US ERNAME_HERE", false)


--
Eric Newton
[email]eric@ensoft-software.com[/email]
C#/ASP.net Solutions developer

"Lauchlan M" <LMackinnon@Hotmail.com> wrote in message
news:%239cwOa2ZDHA.1580@tk2msftngp13.phx.gbl...

> This is silly design on MS's part IMO.
>
> If I have a page Login.aspx and use
> FormsAuthentication.RedirectFromLoginPage it _has_ to go to a default.aspx
> in the same directory, and so _cannot_ go to my secure folder. So I end

up

> with a default.aspx that just redirects to where I really want it to go
> which seems like (and is) a cludge.
>
> And what would happen if my login page _was_ default.aspx? Would it just
> cycle around to itself on successful login?
>
> Sometimes the .net framework is amazing, sometimes you wonder whether MS
> really thought about any of this.
>
> Lauchlan M
>

> > Sorry, FormsAuthentication is hard set to "default.aspx" when doing the
> > RedirectFromLoginPage and/or GetRedirectUrl [which is called by
> > RedirectFromLoginPage]
> >
> > Just execute SetAuthCookie and then if Request.QueryString["ReturnUrl"]

is

> > null, then redirect to where you want:
> >
> > if( [password check passed )
> > {
> > FormsAuthentication.SetAuthCookie( [username], [create persistent
> > cookie] );
> > string returnUrl = Request.QueryString["ReturnUrl"];
> > if( returnUrl == null || returnUrl.Length < 1 )
> > returnUrl = "default.aspx";
> > Response.Redirect( returnUrl, true );
> > }

>
>

[Lauchlan M]

Heh heh.

You might get caught out with that when the framework changes <g>

Lauchlan M

> GetRedirectUrl is one of them, it takes two parameters but doesnt even

TRULY

> use them [it checks the username to see if null and just returns a null if
> so]
>
> In my code, if I use GetRedirectUrl You'll frequently see "string url =
> FormsAuthentication.GetRedirectUrl("SILLY_BOGUS_US ERNAME_HERE", false)