Link to home
Start Free TrialLog in
Avatar of Edwin Bowles
Edwin Bowles

asked on

asp.net getting HTTP Error 404.15 - Not Found

When running a web application from the root directory of the web server, everything works well. When trying to publish the web site to a virtual directory I get the HTTP Error 404.15 - Not Found.User generated image
Avatar of Edwin Bowles
Edwin Bowles

ASKER

When the attached is published to the root directory of a web server, everything works fine. When it is published to a virtual directory I get the error screen displayed earlier.
Default.aspx
Default.aspx.cs
LogOn.aspx
LogOn.aspx.cs
Web.config
Avatar of Manoj Patil
Hey check below steps

    Excluded all the items under the "Account" folder except Login.aspx
    Excluded IdentityConfig and Startup.Auth under the "App_Start" folder
    Excluded IdentityModels under the "Models" folder
    Excluded "Startup" under the "root" folder of the application
    Commented out all the code under "Page_Load" and "LogIn" inside the Login.aspx code file
    Commented out code with "OpenAuthProviders" in the Login.aspx markup

    Added the following key to the "appSettings" section inside the web.config file

    < add key="owin:AutomaticAppStartup" value="false" />

Reference URL : http://stackoverflow.com/questions/24495585/http-error-404-15-the-request-filtering-module-is-configured-to-deny-a-request-w
ASKER CERTIFIED SOLUTION
Avatar of Edwin Bowles
Edwin Bowles

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
The person that originally wrote the code tried to take control of the Authentication process. This seemed to work OK when the user published the Authentication code into the root directory. As soon as you published to a different folder and a web folder , converted to a web application, it would no longer work. I replaced the Response.Redirects in the Master page and the content pages to FormsAuthentication.RedirectFromLoginPage(sys_user_session.userName, true);. Everything seemed to start working.