ASKER
ASKER
The successor to Active Server Pages, ASP.NET websites utilize the .NET framework to produce dynamic, data and content-driven web applications and services. ASP.NET code can be written using any .NET supported language. As of 2009, ASP.NET can also apply the Model-View-Controller (MVC) pattern to web applications
TRUSTED BY
1.) rename Login.aspx (existing) to User.aspx
Create Login.aspx
Codebehind
Page Load
if (Request.ServerVariables["
{
// redirect to dead page
}
else
{
Server.Transfer("User.aspx
}
Granted, if someone went to User.aspx, there's no check, but you don't have the source code to Login.aspx.
The other thing that you could do is create a new login page in the application. Edit the web.config file and turn the tracing on.... after you log in, see what session variables it's setting (if it does it session based), and mimick them on your own login page. If it's forms authentication, then you can just do your own forms auth, and the app should behave as normal.
Just some thoughts...