Try to recreate 502 Bad Gateway Unexpected EOF error by deselecting the SSL checkbox in the Target Server.
Back to the proxy, open the trace session and send a request.
We will got the expected error, but in the trace session, there is no direct indication that the proxy was unable to connect to the Target Server. We just see an error flow info and just went on its fault rule.
This issue in trace session has been raised to us for it would be difficult for the support team to find the target service of the proxy that is failing in case of server downtime.
I think of using Assign Message to indicate a failure on connecting to a target server in case of this 502 error.
But any much better tips on this issue on trace?
Maybe an update on trace UI for this error would be good? What are your thoughts?
We are using Apigee Edge.
Thank you.
LinkedIn
Twitter
