IIS Web application adding return URL

When I copied my .NET web application folder to IIS and added it as a virtual directory, it opened like a charm http://mywebserver/mywebapp.
I then hit publish from my development machine and published on the webserver directly. This was the first time I was doing it and something got messed up.

Now I try to access the web application and it goes to


It looks like it is because of the web.config. But this issue did not come up previously with the same web.config. My default page should be weblogin.aspx. I have added it on the top of list of default documents in IIS.
Anyway, I tried changing a lot of things but the application does not load as needed. Can someone please take me in the right direction?
Who is Participating?
käµfm³d 👽Connect With a Mentor Commented:
You are using Forms authentication, and when your user hasn't logged in, then they are directed to the login page by default, regardless of what page they were trying to originally access. ASP.NET will append the original page that the user was trying to access to the URL as the ReturnUrl, and once the user logins in, he will be redirected to the page they were previously trying to access.

If your actual login page is named weblogin.aspx, then you need to change the value in the loginUrl property (line 2 of your attached file).
Angel02Author Commented:
Thanks. Can I remove the entire forms authentication tag? Do I also need to add the default document tag
       <!--<add value="WebLogin.aspx"/>-->
Should I mention the default document here in web.Config or in the IIS. Default document lists or do not mention at all if I am using forms authentication?
CodeCruiserConnect With a Mentor Commented:
If you put WebLogin.aspx as the login page in the Forms tag, user will get redirected to this page automatically and you don't have to worry about default documents.
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

käµfm³d 👽Commented:
"Default document" is used for when a user does not put a particular page in the URL when coming to your site. You would not use the default document as kind of redirect to your login page--that's not its intent. It basically treats:


...as if the user had entered:


...or whatever default document you specified in your configuration file or within IIS.
Angel02Author Commented:
If the user goes to http://mywebserver/mywebapp, it should be as if the user has entered http://mywebserver/mywebapp/weblogin.aspx.

I changed the forms authentication to
 <forms loginUrl="weblogin.aspx" timeout="2880"/>
and removed the default document from web.config and in IIS.

Now when I browse the web application from IIS, it keeps loading then displays the weblogin.aspx as plain text (without images and css) and then it says "localhost not responding". I can't figure out what is going on.

Is this all just because I did something when I published?
So it is working really. Now you have another problem.

What does weblogin.aspx contain?
Angel02Author Commented:
It is a simple page to enter login credentials. Only additional thing in it is it accesses a master page.
Interestingly, when I copied the project to a new location C:\WebSites\MyWebApp (Previously it was at c:\inetpub\wwwroot) and added a new virtual directory with  C:\WebSites\MyWebApp as the physical path, everything got back to normal. The website is now loading perfectly. So I am going to leave it like that.

Is there anything I need to worry about?
Can't think of if it is working.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.