iFinity

I am running FUP 5.1.0 on DNN 4.9.5. If I request a URL in which the parent page of the requested page is mis-spelled I get an ASP.NET exception. Here's an example:

Requested: /COMMOONITY-BLOG/Blog.aspx
Real URL: /COMMUNITY-BLOG/Blog.aspx

However if the requested page name is mis-spelled, this is handled gracefully with the parent page being opened, e.g.

Requested: /COMMUNITY-BLOG/Blg.aspx
Real: /COMMUNITY-BLOG/Blog.aspx

I notice the error is not being thrown by the provider itself. I am hoping you can still "fix" it because it's a big problem when a parent page is renamed and all the links to the child pages in Google etc stop working!

Here's the full error:

System.Exception: Unhandled Error: ---> System.Web.HttpException: The file '/COMMUNITY/Ski-Reports.aspx' does not exist. at System.Web.UI.Util.CheckVirtualFileExists(VirtualPath virtualPath) at System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) at System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) at System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig) at System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) --- End of inner exception stack trace ---

Many thanks

All the above details came from the DNN event log. What you get on the screen is (as you said) an ASP.NET 404 exception.

I would like to handle the 404 by redirecting to the home page, but the trouble is I already have added  defaultRedirect="/Install/UnderConstruction.htm" to the customErrors element in web.config (to catch "real" ASP.NET exceptions like the DB connection is down). Is there a way to handle the 404 separately from other exceptions?

OK thanks, I'll check out using a different handler.

However I would like to bug you a bit more about whether this problem can be handled more gracefully by the FUP :)

It's a fairly common, or at least predictable, scenario (that a page gets renamed), and the 404 arises when using the FUP but not when using native DNN URLs (because the tabid param remains constant). So, to someone switching from native DNN urls, it occurs as a slight downside to the FUP (although the positive aspects are so great I would never switch back). I do realise that in a non-DNN/non-dynamic website, changing a part of a page's URL would inevitably lead to a 404 and that is just a fact of life.

So, would you consider adding a parameter to the config that controls where the user is redirected to when the requested URL cannot be matched against any DNN tab? Something like a "404Redirect" parameter?

Thanks