This is because of a server setting regarding error pages. IIS and ASP.NET has two individual "error pages", where ASP.NET is the regular yellow page, and IIS errorpages can be either the simple one that you get, or a detailed one with further details on the error, or the actual response that is generated if the request actually serves any content. The simple one overrides the actual response, which isn't really useful in these cases. It all comes down to when you return http status 500, then the IIS- page kicks in.
You can overcome this by adding existingResponse="PassThrough" in httpErrors under <system.webServer> like this: <httpErrors errorMode="Custom" existingResponse="PassThrough" /> Good luck! Regards, Jimmy On Oct 26, 3:44 pm, Tomek Pluskiewicz <[email protected]> wrote: > Hi > > I have a problem getting rescues to work in production. > > On local IIS 7.5 everything is fine. Rescues intercept exceptions and > a rescue view is shown. > > Unfortunately on remote development server instead of the rescue view, > a generic "500 - Internal server error. There is a problem with the > resource you are looking for, and it cannot be displayed." page is > shown. And not even the yellow ASP.NET exception page. > > This is clearly an issue with rescues. When rescue is removed, that > yellow page is shown. > > Development server also runs IIS 7.5. > > Regards > Tomasz -- 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.
