Copied to clipboard

Flag this post as spam?

This post will be reported to the moderators as potential spam to be looked at


  • Robert Hughes 87 posts 110 karma points
    Jan 16, 2013 @ 21:47
    Robert Hughes
    0

    Unwanted Trace Output on Custom Error Handling

    I am having a weird issue at the moment.

    We have an Umbraco site and handle unhandle exceptions through the standard Application_Errror global.asax event.

    Our code is basically this - which in theory should simply render the friendly error page while logging the error. An ideal scenario I believe.

    logger.ErrorException("Error occurred accessing: " + Request.Url.AbsoluteUri, error);
    Response.TrySkipIisCustomErrors = true;
    Server.ClearError();
    Response.ClearContent();
    Response.ClearHeaders();
    Response.StatusCode = 500;
    Server.Transfer("~/error.aspx");

    This works fine on a standard web application but in Umbraco my custom error page is successfully rendered but underneath it the full request trace output is rendered which is not ideal for security and user-experience reasons.

    Anyone else had a similar experience - not sure if it has anything to do with Umbraco but like I say I don't get any stack trace in a standard web application.

    Umbraco 4.9.1 .NET 4.0 IIS 7.5

    cheers,

    Robert

     

     

     

     

Please Sign in or register to post replies

Write your reply to:

Draft