11 Jan
2013
11 Jan
'13
9:26 a.m.
On 11.01.2013 00:47, LANGLOIS Olivier PIS -EXT wrote:
Hi,
The following 2 lines has caused me some problems:
curl_easy_setopt(curl, CURLOPT_LOW_SPEED_LIMIT, 1024L); curl_easy_setopt(curl, CURLOPT_LOW_SPEED_TIME, 10L);
[...]
I am wondering if I am the only and first user having this problem and how it could be solved cleanly for everyone upstream.
We could set the limit to 1L then curl would only abort if no data has been transferred so slow connections would still be allowed, but servers no responding wouldn't be much of a problem.