Yes, the exact same setup works in another site, as I said. I'm not really sure where the rescue-controller would hijack the exception and bypass IIS error handling, maybe someone can enlighten me.
On Oct 21, 12:53 pm, Daniel Hölbling <[email protected]> wrote: > Have you set the RescueController on the Controller that throws the error? > Or did you configure it through Web.config? > > On Wed, Oct 21, 2009 at 11:19 AM, Jimmy Shimizu > <[email protected]>wrote: > > > > > I have a an issue with a website where the rescue-controller doesn't > > seem to kick in, instead I just recieve this message: > > > "The page cannot be displayed because an internal server error has > > occurred." > > > I have another site running on the exact same server, with almost > > identical web.config, and the same monorail-configuration and the exact > > same RescueController defined. The error occurs, because of a > > AuthorizationFailedException (because of a PrincipalPermission-attribute > > on my methods in the controller) when not logged in, however I want the > > Rescue to handle these error-pages. > > > Anyone has a hint on where to look? It's probably really simple, but I > > just can't figure out where to start. > > > /Jimmy > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en -~----------~----~----~----~------~----~------~--~---
