No Answers
- Newest
- Most votes
- Most comments
Relevant content
- asked 2 years ago
- asked 5 months ago
- asked 10 months ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- How do I customize my nginx configuration to modify the "client_max_body_size" in Elastic Beanstalk?AWS OFFICIALUpdated a year ago
re "a long running web request", can you please update the post with some examples of such requests? this will help us in offering possible answers, and other people who search the web for similar issues. For example, does this mean your application container performs some sort of slow computation before producing response?
The underlying proxy that powers "public endpoints" feature has the "idle connection" timeout of 60 seconds, so this is the short answer as to why you get these timeouts.
Thank you Pavel for the response.
It's the server that the container is performing the request which is performing time consuming computations. Is there any way the idle timeout can be increased on the proxy to make the content available to the container?
Neeraj, unfortunately this idle time out is currently not modifiable for public endpoints. Perhaps the server application can be changed with that limitation in mind? E.g. you can have an API that starts an expensive computation and responds immediately with an ID which can be used with a separate API that allows you to check if the computation for the given ID has concluded or still in progress. Another approach for long running HTTP interactions is to use https://en.wikipedia.org/wiki/WebSocket Both of these approaches would work well with the idle timeout as it is now.