-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
API call timeout #32
Comments
Did you change the |
having a similar issue for streaming a .mp4 video with timeout set to 10000 Error: API call timed out |
I have the same problem when try to proxy request with body. The same request without body works well. |
It is not a clue but may be it will help somebody. Solution for me was to change content-type from 'application/json' to 'text/plain'. Direct request with content type 'application/json' works well. |
This is also an issue for me. I'm using |
Hi all - for me, the issue was something with bodyParser. Moving my |
This worked for me |
I always experienced this:
Error: API call timed out
at Function.Error.create (/root/proxy/node_modules/simple-errors/index.js:25:11)
at Function.Error.http (/root/proxy/node_modules/simple-errors/index.js:68:21)
at unhandledApiError (/root/proxy/node_modules/express-request-proxy/lib/proxy.js:254:25)
at Request. (/root/proxy/node_modules/express-request-proxy/lib/proxy.js:86:7)
at emitOne (events.js:121:20)
at Request.emit (events.js:211:7)
at Timeout._onTimeout (/root/proxy/node_modules/request/request.js:848:16)
at ontimeout (timers.js:498:11)
at tryOnTimeout (timers.js:323:5)
at Timer.listOnTimeout (timers.js:290:5)
I found that it caches the incomplete result even it is timeout. How to avoid that?
The text was updated successfully, but these errors were encountered: