My first guess would be that LoginPage.aspx was either redirected through some simple HTML which is missing now or the server was set to redirect to LoginPage.aspx by default. Look up the control panel, there might be some settings that allow you to set default page.
My 2 cents On Mon, Mar 29, 2010 at 2:26 PM, OccasionalFlyer <[email protected]> wrote: > I am about four months into being the administrator for an ASP.NET- > based web site (volunteer). Our ISP recently "migrated" the site to a > new platform. I didn't do anything for this. Now that it is done, > suddenly at least two links are broken. The most significant is the > link to the LoginPage.aspx. I guess there's a big piece of ASP I > don't understand yet because I can't find anywhere on Default.aspx or > the master page that has the exact path to the LoginPath.aspx page. > Nevertheless, this used to work all the time. Now that it is > migrated, it does not work. > > Now, I was not part of this but the web site's structure is > /ASP.NET/IBR-MERGE/LoginPage.aspx. I don't understand how the web > server knows to look down here for the file since I don't see that > path in Default.aspx. Therefore, I don't know where to go to fix the > broken path . How does ASP.NET know where to look for a given page, > since it is clearly not using a simple URL HTML "link"? I don't > recall seeing a discussion of this in the ASP.NET 3.5 book I have been > reading. If there's a good explanation someplace, I'd be happy to > read it. Thanks. > > Ken > > To unsubscribe from this group, send email to dotnetdevelopment+ > unsubscribegooglegroups.com or reply to this email with the words "REMOVE > ME" as the subject. > To unsubscribe from this group, send email to dotnetdevelopment+unsubscribegooglegroups.com or reply to this email with the words "REMOVE ME" as the subject.
