SharePoint world of ECM and Information Management

Yesterday I was working on the custom error handing for the SharePoint. They wanted to provide the consistent look and feel for all errors that you can expect – from 301 to 500. It’s quite simple task and what you just need is to turn off custom errors in web.config and set customized error pages in IIS.

The reason we customized error pages via IIS is that we didn’t want to mess up with customization of OOTB pages, and our pages have several pictures. Rendering pictures for “unauthorized” and “forbidden” errors under SharePoint in problematic. That’s why we just redirect user to another site with custom error pages.

The only issue we experienced is customizing 403 page, when SharePoint handled it gracefully redirecting us to _layoutsAccessDenied.aspx page. To avoid such behavior I end up with URL parsing and status code analysis via custom HTTPModule.

I published this solution as SharePoint feature on the CodePlex site http://sharepoint403page.codeplex.com/