Hi Custom 404 Team,
Firstly thanks for an excellent and clever plugin that fills a much needed gap.
I was wondering if you could help shed some light on an error we are experiencing with the plugin.
We seeing an unhandled exception which looks like it is being thrown during the rendering of the intermediate NotFound.aspx page.
See the stack trace below. I can replicated it by opening the debug tools in Chrome at which point Chrome tries to find a .map file. However, that is just a way I can replicate it, there are other requests coming in causing an error too.
I have double checked, and we have followed the implementation correctly, and the 404 page loads correctly when I enter a non-existent URL on the site.
It is not preventing anything from happening on our site, however we would like stop it from occurring.
Have you seen this error, and/or have any ideas about how to prevent it?
Thanks and kind regards,
Stuart
Here is the stack trace:
[1] Exception of type 'System.Web.HttpUnhandledException' was thrown. at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) [2] Object reference not set to an instance of an object. at ASP.notfound_aspx.__Render__control1(HtmlTextWriter __w, Control parameterContainer) at System.Web.UI.Control.RenderChildrenInternal(HtmlTextWriter writer, ICollection children) at System.Web.UI.Page.Render(HtmlTextWriter writer) at System.Web.UI.Control.RenderControlInternal(HtmlTextWriter writer, ControlAdapter adapter) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
Hi @Stuart Harris. Thank you for your kind words and for sharing this issue with us.
We were not aware of this behavior. We'll have a look at it and let you know.
Thanks.