502 - Unexpected EOF errors on connection between Apigee to Azure Front Door

My company uses Apigee Edge Public Cloud and we have some target servers hosted in Azure via "Front Door".  The clients that call our Apigee proxies are getting intermittent '502 - Unexpected EOF' failures.  Apigee support has said its because Front Door is not handling connection pooling correctly, but Azure support says everything is working correctly and cannot see problems.  

Apigee asked for 'TCP Dump' from Azure, but Azure support says they cannot provide this, so we are at a stalemate with support.

Our only known work-around is to change our apigee proxies to have an extra header "Connection:close" before they call Azure. This tells Apigee not to use "Connection Pooling", but is an anti-pattern

Is anyone else seeing problems between Apigee and Azure Front door or have any better solutions?

0 0 186
0 REPLIES 0