Solved

IIS Web application adding return URL

Posted on 2014-03-17
8
1,377 Views
Last Modified: 2014-03-23
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

http://mywebserver/mywebapp/Account/Login.aspx?ReturnUrl=%2fmywebapp

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?
EE-webconfig.txt
0
Comment
Question by:Angel02
  • 3
  • 3
  • 2
8 Comments
 
LVL 74

Accepted Solution

by:
käµfm³d   👽 earned 350 total points
Comment Utility
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).
0
 

Author Comment

by:Angel02
Comment Utility
Thanks. Can I remove the entire forms authentication tag? Do I also need to add the default document tag
 <defaultDocument>
<files>
       <!--<add value="WebLogin.aspx"/>-->
      </files>
    </defaultDocument>
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?
0
 
LVL 83

Assisted Solution

by:CodeCruiser
CodeCruiser earned 150 total points
Comment Utility
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.
0
 
LVL 74

Expert Comment

by:käµfm³d 👽
Comment Utility
"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:

    http://www.example.com/

...as if the user had entered:

    http://www.example.com/index.html

...or whatever default document you specified in your configuration file or within IIS.
0
Free Gift Card with Acronis Backup Purchase!

Backup any data in any location: local and remote systems, physical and virtual servers, private and public clouds, Macs and PCs, tablets and mobile devices, & more! For limited time only, buy any Acronis backup products and get a FREE Amazon/Best Buy gift card worth up to $200!

 

Author Comment

by:Angel02
Comment Utility
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?
0
 
LVL 83

Expert Comment

by:CodeCruiser
Comment Utility
So it is working really. Now you have another problem.

What does weblogin.aspx contain?
0
 

Author Comment

by:Angel02
Comment Utility
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?
0
 
LVL 83

Expert Comment

by:CodeCruiser
Comment Utility
Can't think of if it is working.
0

Featured Post

Do You Know the 4 Main Threat Actor Types?

Do you know the main threat actor types? Most attackers fall into one of four categories, each with their own favored tactics, techniques, and procedures.

Join & Write a Comment

Running classic asp applications under Windows Server 2008 R2 (x64) and IIS 7 is not as easy as one may think. It took me a while to figure it out while getting error 8002801d a few times. After you install the OS you will need to install the fol…
The ECB site provides FX rates for major currencies since its inception in 1999 in the form of an XML feed. The files have the following format (reducted for brevity) (CODE) There are three files available HERE (http://www.ecb.europa.eu/stats/exch…
In this seventh video of the Xpdf series, we discuss and demonstrate the PDFfonts utility, which lists all the fonts used in a PDF file. It does this via a command line interface, making it suitable for use in programs, scripts, batch files — any pl…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

8 Experts available now in Live!

Get 1:1 Help Now