Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The CustomErrors directive in my web.config is working, except that for 404’s, IIS serves a 302 redirect with no ContentType header. This causes firewalls to block the response, and clients never get to the custom error page. Note I’m using IIS7, MVC (razor), ELMAH, and support various browsers.
<customErrors defaultRedirect="~/Site/Error" mode="RemoteOnly" />
How can I get my a reasonable Content-Type header on all my CustomError redirections, or otherwise fix the problem?
You could try writing a custom HTTP module like this person did here:
http://www.colincochrane.com/post/2008/01/ASP-NET-Custom-Errors-Preventing-302-Redirects-To-Custom-Error-Pages.aspx