Contents tagged with Application Request Routing
-
Winhttp Tracing Options for Troubleshooting with Application Request Routing
In my earlier blog “ 502.3 Bad Gateway “The operation timed out” with IIS Application Request Routing(ARR) “ I referenced links for gathering Winhttp tracing for troubleshooting 502.3 issues.
-
Overview of Application Request Routing’s Health Check features
I had a recent question about the ARR health check features which resulted in this overview. Hopefully this is helpful to those of you setting up new ARR deployments.
-
502.3 Bad Gateway “The operation timed out” with IIS Application Request Routing(ARR)
When working with ARR deployments one of the errors you might see is 502.3 Bad Gateway. The 502.3 means while acting as a proxy ARR was unable to complete the request to the upstream server and subsequently send a response back to the client. This can happen for multiple reasons including , failure to connect to the server , no response from the server, or server took too long to respond (time out).
-
Missing Failed Request Tracing (FREB) trace Areas ?
I was recently working with a colleague to troubleshoot an issue using Application Request Routing (ARR) and wanted to use the trace areas provided by ARR to see the events this logged.