Properly Using Custom Error Pages in ASP.NET

Earlier this week I started with a rant about ASP.NET and Search Engine Optimization and was really tired of my platform being dissed as a good platform for optimized sites. One of the complaints raised by the article was the way ASP.NET handles custom errors. The complaint centers around two status codes being generated, first a 302 or temporary redirect is sent. Then a 200 status code is sent for a successful request. This is actually the proper way to indicate the custom error page process and I will explain why.