Hi @Olu
Thanks for quick response.
Are there any changes or difference in the gateway config and API definition? Is it exactly the same?
Yes, all the configurations and definitions are same earlier. you can refer our conf here DRL Rate-limiting failing edge case 1-2 calls in TYK v4.3.4 - #4 by Mohit_Kumar
This would mean its not occurring at random or after a number of requests?
What is the flow of the request? I assume hitting the upstream works as expected.
This error was coming when we were trying to download data above 80-90 mb in size. till 70-80 mb API is working fine. With upstream URL, all APIs were success with data up to 500 mb.
Also how are the certs generated?
Currently we have self signed certificated generated & configured.
Today we have made below changes in our tyk.conf, that resolved the issue for now:
“flush_interval”: 1,
“read_timeout”: 2000
“write_timeout”: 2000
“proxy_default_timeout”: 1200
only proxy_default_timeout was changed from 600 to 1200, others confs added newly.
are these configurations looks OK & recommended for streaming API use cases (where 300-500 mb data is being transferred).
Also on removing enable_http2 conf also we see HTTP1.1 request, is that OK.