Comments on: 404 and 403 Error Pages in ASP.NET http://codehill.com/2009/01/404-and-403-error-pages-in-aspnet/ Premium Web Application Development Fri, 11 May 2012 06:51:11 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: KalC http://codehill.com/2009/01/404-and-403-error-pages-in-aspnet/#comment-133252 KalC Thu, 03 Mar 2011 17:52:22 +0000 http://www.codehill.com/?p=78#comment-133252 I ran into the same problem as Sangam... and Amgad's solution solved the problem. Thanks. I ran into the same problem as Sangam… and Amgad’s solution solved the problem. Thanks.

]]> By: Amgad Suliman http://codehill.com/2009/01/404-and-403-error-pages-in-aspnet/#comment-36 Amgad Suliman Fri, 30 Jan 2009 15:24:29 +0000 http://www.codehill.com/?p=78#comment-36 Hey sangem, what I understood from your comment is you created the whole project in 1 folder and restricted access to logged in users only. If this is the case, the easiest way to solve this problem is to create a sub folder and put in it all the pages that require logging in. And leave the login and noaccess pages in the root folder. Then restrict access to the sub folder using ASP.NET's Configuration web app. This way anonymous users can browse the whole website except the restricted folder. Please try it out and let me know what happens. Hey sangem, what I understood from your comment is you created the whole project in 1 folder and restricted access to logged in users only. If this is the case, the easiest way to solve this problem is to create a sub folder and put in it all the pages that require logging in. And leave the login and noaccess pages in the root folder. Then restrict access to the sub folder using ASP.NET’s Configuration web app. This way anonymous users can browse the whole website except the restricted folder. Please try it out and let me know what happens.

]]> By: sangam uprety http://codehill.com/2009/01/404-and-403-error-pages-in-aspnet/#comment-35 sangam uprety Fri, 30 Jan 2009 10:31:57 +0000 http://www.codehill.com/?p=78#comment-35 In my case, the noaccess.aspx page is never displayed. Rather the the user is prompted with the login page. If user logins successfully with the authorized account, she will be redirected to the page, otherwise the login page continues to prompt. I even tried to catch access denied case from the global.asax page, but no success. I don't why this happens. Currently I am catching all these in the login page and then redirect the user to the access denied page [noaccess.aspx]. Regards, Sangam In my case, the noaccess.aspx page is never displayed. Rather the the user is prompted with the login page. If user logins successfully with the authorized account, she will be redirected to the page, otherwise the login page continues to prompt.

I even tried to catch access denied case from the global.asax page, but no success. I don’t why this happens. Currently I am catching all these in the login page and then redirect the user to the access denied page [noaccess.aspx].

Regards,
Sangam

]]>