Response.TrySkipIisCustomErrors not working

I have a page where i want the page to return a 404 response but remain on that page. Please don’t ask why – the client wants it that way even after i discussed it with him.

I’ve got a .net page written in C# running under iis 8 and the app pool is configured to run under 4.0 integrated mode

When i set the statuscode to 404 in the page, it gets sent to the custom 404 error page that’s set up for this site. After googling i found another post on SO mention using Response.TrySkipIisCustomErrors. From what i read it sounds like it’s exactly what i need. I tried setting it to true and it had no effect in the behavior of the page – still get sent to the customer 404 error page that’s setup in iis.

Anyone have any ideas why this isn’t working?

Answers:

Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.

Method 1

Well – this is a first. First time I managed to find the answer before hitting the submit button 🙂

Found this IIS.net article:
http://www.iis.net/configreference/system.webserver/httperrors
which then lead me to find this:
http://msdn.microsoft.com/en-us/library/ms690576(v=vs.90).aspx

Scroll down to the part that explains what the options for existingResponse mean. I had mine set to Replace which means it ignores TrySkipIisCustomErrors completely. Changed it to Auto and it’s working.


All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0

0 0 votes
Article Rating
Subscribe
Notify of
guest

0 Comments
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x