When we get a 400 HTTP response before I enabled error passthrough in the web.config it'd display "Bad Request" as a string.
With passthrough it's now displayed as "The page cannot be displayed because an internal server error has occurred."
This issue doesn't occur on our local versions and only once on our server hence why we believe it be an issue with IIS. Although I'm unsure as to why the message would change once passthrough is enabled unless something else is then trying to handle it.
We have code setup to handle the 400 response and output a message on the current page but due to these strings it's causing our code to break. Again only once on our server and not locally.
Anybody got any ideas of what else could be causing the response handling?
tl;dr something is still handling 400 responses after enabling error passthrough in web.config.
IIS 400 Error Handling
When we get a 400 HTTP response before I enabled error passthrough in the web.config it'd display "Bad Request" as a string.
With passthrough it's now displayed as "The page cannot be displayed because an internal server error has occurred."
This issue doesn't occur on our local versions and only once on our server hence why we believe it be an issue with IIS. Although I'm unsure as to why the message would change once passthrough is enabled unless something else is then trying to handle it.
We have code setup to handle the 400 response and output a message on the current page but due to these strings it's causing our code to break. Again only once on our server and not locally.
Anybody got any ideas of what else could be causing the response handling?
tl;dr something is still handling 400 responses after enabling error passthrough in web.config.
is working on a reply...