Best way to implement a 404 in ASP.NET
- by Ben Mills
I'm trying to determine the best way to implement a 404 page in a standard ASP.NET web application. I currently catch 404 errors in the Application_Error event in the Global.asax file and redirect to a friendly 404.aspx page. The problem is that the request sees a 302 redirect followed by a 404 page missing. Is there a way to bypass the redirect and respond with an immediate 404 containing the friendly error message?
Does a web crawler such as Googlebot care if the request for a non existing page returns a 302 followed by a 404?