The error occurs when you leave a page before it finishes processing, which happens on a redirect. This is usuallly handled gracefully, but you are probably calling it in a constructor and hence the error is popping up.
BUT, this functionality (redirecting unauthenticated users) is already built into the ASP.NET model, why are you reinventing the wheel? Making it work is not much more than a few settings in the web.config file. Here's an overview of how the built in authentication works. Save yourself a lot of time and frustration and check it out. http://www.ondotnet.com/pub/a/dotnet/2003/01/06/formsauthp1.html HTH -- Dean Fiala Very Practical Software, Inc http://www.vpsw.com ------------------------ Yahoo! Groups Sponsor --------------------~--> $4.98 domain names from Yahoo!. Register anything. http://us.click.yahoo.com/Q7_YsB/neXJAA/yQLSAA/saFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
