Hi Everyone!
I'm evaluating ARR for use as a reverse proxy in front of several self-hosted ASP.NET Web API applications running within Windows services. The Web API services return primarily JSON data and use the HTTP status code of the response to communicate status to the calling client. Recently I noticed that one of our API methods encountered an exception that causes a 500 Internal Server Error response that should be accompanied by error information in JSON format sent back to the client. This works correctly when the Web API service is hit directly using Fiddler, but when it sits behind ARR it seems like ARR intercepts the 500 error and returns a 502 Bad Gateway error with an HTML page.
Is this the standard behavior for ARR to intercept 500 responses from upstream servers and report them back to the calling client as Bad Gateway results? If so, any way to get around that so that ARR is simply returning to the client application exactly what it received from the upstream server, even if it is a 500-type error?
Thanks!
Rich