I really can't tell. It looks like you have a problem with long-running connections but there's nothing in libcurl that cares about age or how much data that has been sent so I really cannot understand how this can be a libcurl issue.

To tell if this is a libcurl issue, you probably need to show that you can do this kind of long-living connections without libcurl just fine and that you only see these problems when using libcurl.

---
** [bugs:#1275]  Timeout after multiple requests with curl_easy_reset**
**Status:** pending-needsinfo
**Created:** Wed Sep 04, 2013 07:36 AM UTC by lietus
**Last Updated:** Wed Sep 18, 2013 07:21 AM UTC
**Owner:** Daniel Stenberg
Running on iPad, iOS 6.0.1, libcurl/7.29.0 OpenSSL/1.0.1e zlib/1.2.5.
I'm executing multiple HTTP POST requests with same content size - uploading big file in chunks.
After few requests are completed, one request gets stuck until timeout happens.
Which request will timeout is always more or less the same - it depends on request size being sent.
For example, uploading:
4 MB requests will always result in 2th requests stuck;
2 MB requests - 4th requests stuck;
100000 B requests - 58th requests stuck;
10000 B requests - ~316th requests stuck (+-);
However, I noticed that if I call curl_easy_init instead of curl_easy_reset, this problem goes away. What doesn't curl_easy_reset do for this to happen?
Also, after timeout happens, I call curl_easy_reset and setopt all values needed, that also fixes problem for another few requests (same pattern applies).
curl_easy_init cannot applied here because it would slow down other requests that come though this code.
Thanks,
Vincas
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.