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.
I think that it should work. I'll test it on my network and report it back on the list with a patch if it is successful. Thank you, ________________________________ CONFIDENTIALITY : This e-mail and any attachments are confidential and may be privileged. If you are not a named recipient, please notify the sender immediately and do not disclose the contents to another person, use it for any purpose or store or copy the information in any medium.