> This is perhaps a tangent, but I could not get > CURLOPT_SERVER_RESPONSE_TIMEOUT_MS to do anything at all.
Hmmm, it seems CURLOPT_SERVER_RESPONSE_TIMEOUT_MS only works for protocols that use libcurl's internal "ping-pong" abstraction, which includes FTP, IMAP, POP3 and SMTP but not HTTP. I don't know if there's a good reason behind that. You may need to use CURLOPT_LOW_SPEED_TIME and CURLOPT_LOW_SPEED_LIMIT instead, but that has a 1 second minimum timeout. An alternative is to just set an overall timeout with CURLOPT_TIMEOUT_MS but there's a danger that on an overloaded system it will timeout before the request is sent and logged. -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-library Etiquette: https://curl.se/mail/etiquette.html
