I have our website on a Windows machine , under IIS10

Within the website there is an aspx page which delivers our stocks, not directly but making first a Http call to a Web Connection Server ( which returns a real time list)

All is perfect except the situation when FoxPro needs more than 3 seconds to produce the list. In case Foxpro fails to answer in less than 3 seconds, the server returns:
504 Gateway Time-out The server didn't respond in time.

By default, IIS 10 sets QueueConnectionTestTime at 3 seconds ; I modified it to 10 seconds but still get the error

QueueTimeout and ScriptTimeout is set to 90 seconds ; HttpRequest ExecutionTime at 120 second Intervals above are set both for Foxpro application and website asp

IIS log files returns 200-Succesful operation

Any suggestion ?

What are those Queue settings you're setting? They are ASP classic settings and I think they have absolutely no effect on ASP.NET Web site operation.

Timeouts are tricky on IIS because there tend to be several. ASP.NET has a timeout, IIS has a timeout, Web Connection has a timeout. However, none of those should have 3 second timeout - I think the IIS default is 20 seconds so I don't think the issue is on the server.

The Gateway in the message seems to suggest it's either a proxy or some other intermediary in the HTTP pipeline that's causing the timeout.

+++ Rick ---