+1-888-365-2779
Try Now
More in this section

Forums / Bugs & Issues / error handling, possible bugs?

error handling, possible bugs?

4 posts, 0 answered
  1. SelAromDotNet
    SelAromDotNet avatar
    912 posts
    Registered:
    18 Jul 2012
    04 Aug 2008
    Link to this post
    now that we've gone live, I'm getting a few error reports here and there, and while fixing these few issues, I've noticed something regarding how sitefinity handles errors:

    1) 404 errors: mapping to the sf404.aspx page is a great way to handle the extensionless urls, and the fall-through behavior of a non-existant page works as expected, user is returned a 404 error along with the requested path in the querystring under aspxerrorpath.... however if the user is requesting a document, such as a pdf, or jpg, etc... they are not shown the correct requested path but instead see the querystring with aspxerrorpath=/sf404.aspx. This is confusing to users, as this is not the page they requested.

    2) Default Redirect: if an unhandled exception occurs and there is no specific redirect in the web.config errors section, the user is redirected to the default redirect page, which is fine. However, the aspxerrorpath is shown to be /sitefinity/cmsentrypoint.aspx! This is really not good because the users should not know what system we are using to maintain our website!
  2. Nikifor
    Nikifor avatar
    232 posts
    Registered:
    18 May 2013
    06 Aug 2008
    Link to this post
    Hi SelArom,

    The first point of your report covers an already known issue which was downgraded since the 3.2 SP2 version. It is included for fixing in our road map so it will be addressed in the next Sitefinity release. We apologize for the inconvenience.
    As for the second part of your request, it is always good to have more custom error pages defined in your web.config. In case this is not an option for you, you can redirect all Unhandled exception errors to a concrete page which distinguish the /sitefinity/cmsentrypoint.aspx page. just make the following change in the web.config:
    <customErrors mode="On" defaultRedirect="....."
    You can set a global redirect for your project by setting a value for the DefaultRedirect attribute.

    Best wishes,
    Nikifor
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  3. SelAromDotNet
    SelAromDotNet avatar
    912 posts
    Registered:
    18 Jul 2012
    06 Aug 2008
    Link to this post
    thank you for your reply, I don't mean to sound like a broken record as I didn't realize these errors are all related...

    that being said, I do have a default redirect, but whenever the error occurs and the user is shown that error, the errorpath is appended to the url as a querystring, and the path is shown to be sitefinity/cmsentrypoint.aspx.
  4. Ivan
    Ivan avatar
    478 posts
    Registered:
    16 Jun 2015
    11 Aug 2008
    Link to this post
    Hello SelArom,

    I have just reproduced the behavior you are talking about and the aspxerrorpath query string displays the URL of the page I was looking for (in my case thispagedoesnotexist.aspx). This is the URL:

    http://localhost:3040/ApplicationEvents/en/nopage.aspx?aspxerrorpath=/ApplicationEvents/thispagedoesnotexist.aspx

    nopage.aspx is my default redirect.

    Could you please tell us which version of Sitefinity you are using, since I was not able to reproduce the described behavior with the latest release.

    I am sorry for not being able to help you further at this point.

    Greetings,
    Ivan
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
Register for webinar
4 posts, 0 answered