Hi all,
I am using the Asp.net 2.0 login control in my application.
I have not set the control's DestinationPageUrl property because O want the user to be redirected to the originally requested URL after being authenticated.

This works great if the user is able to login succesfully in the first attempt but if the user fails the first few times and then is able to login successfully, the page is not redirected to the originally requested URL but it reloads the login page again.

How can I get around this problem.?

Regards,
--Monika

Do you mean that you handle authentication and redirection your self? If so, you could save PreviousPage property (or the URL behind that) at page_load when IsPostBack is false. After successful authentication, just redirect user back to saved URL.

Just take notice that some personal firewalls removes HTTP_REFERRER header from query so you need to write some fallback code redirects user to front page for example (or do something really fancy and maintain browser history at the server using session).

No, I dont handle the redirection. I havent specified any redirection url bcoz I want to go to the originally requested webpage after user is successfully logged in.

This works if the user successfully logs in the first attempt but if he succeeds after 1 or 2 attrempts , then the same login page is loaded instead of taking the user to the originally request web page.

How can I fix this problem? Is this a bug with Microsoft login control or some error from my side?

--Monika

Can you show us your code?

It shouldn't be like that. ASP.NET keeps track of the originally requested page in the query string. Even after repeated logion failures, the page should still be there in the query string. Once you log on, you should be taken to the initially requested page....

Imar


---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

Well, here is the catch..!

In my Login control I have FailureAction = "RedirectToLoginPage"
Hence after every failure it goes to login page...then I have some custom error message for display.

The user logs in back successfully and then is not taken to the originally requested URl but to the LoginPage.

If I take off the FailureAction Part in the code.., it works fine!


--Monika.

Well, in that case, drop the FailureAction setting and handle the custom error message in LoginError.

Would that work for you?

Imar


---------------------------------------
Imar Spaanjaars
http://Imar.Spaanjaars.Com
Everyone is unique, except for me.
Author of ASP.NET 2.0 Instant Results and Beginning Dreamweaver MX / MX 2004

Yes...that works!

Thanks,your replies helped me look better into the code!

--Monika