API Proxy timeout - Page 2

hari_vr · 07-18-2017 11:35 PM

My client is an Apigee Cloud customer and we have an issue with timeouts.

As per the documentation here,

Cloud customers, who can't modify the Edge timeouts, can also configure an API proxy timeout, as long as the timeout is shorter than the standard Edge message processor timeout of 57 seconds.

Our backend application sometimes takes as much as 300 seconds to respond back. So when this happens, while the message processor is perfectly ok with waiting for the backend to respond (io.timeout.millis, connect.timeout.millis and keepalive.timeout.millis set to appropriate values), the router responds back with a 504 Gateway Timeout error in HTML

	<!DOCTYPE html>
<html>
    <head>
        <title>Error</title>
        <style>
    body {
        width: 35em;
        margin: 0 auto;
        font-family: Tahoma, Verdana, Arial, sans-serif;
    }
</style>
    </head>
    <body>
        <h1>An error occurred.</h1>
        <p>Sorry, the page you are looking for is currently unavailable.
            <br/>
Please try again later.
        </p>
    </body>
</html>

So how do I ensure that my client does not get this error back for a transction that takes longer than 57 seconds?