Are there scenarios where Kong 0.14.1 won't retry a request?

[pladdypants]

I’ve run into a scenario where it looks like Kong gets a 502 response from an upstream API but rather than retry, it passes the 502 back to the client. I say “looks” like because I’m having trouble reproducing and it’s intermittent throughout the day and distributed across our API definitions.

Are there any scenarios where Kong will not retry an API call even though it’s configured to do so? We use the default 5 retries on our API definitions.

[hbagdi]

@pladdypants

Are there any scenarios where Kong will not retry an API call even though it’s configured to do so? We use the default 5 retries on our API definitions.

Those retries are for TCP timeouts and not HTTP retries.