Hello,
Last I checked it translated directly to cURL's CURLOPT_TIMEOUT
option[1] and this is used, AFAIK, for all outbound HTTP requests.
Because it tracks the entire request length, the need to increase it
for Orthanc (which often has to perform large transfers) is very common
in our experience.
I haven't yet confirmed that it disregards activity on the connection
(i.e. the timeout won't reset every time a chunk of data is received on
the socket to time out after X seconds of inactivity, but rather times
out exactly X seconds after the request started). From the
documentation, I assume it is so.
(Off-topic, but related:)
I've always meant to submit a PR to allow the use of
CURLOPT_LOW_SPEED_* as sensibly suggested in the cURL documentation:
"Since [CURLOPT_TIMEOUT] puts a hard limit for how long time a request
is allowed to take, it has limited use in dynamic use cases with
varying transfer times. You are then advised to explore
CURLOPT_LOW_SPEED_LIMIT, CURLOPT_LOW_SPEED_TIME or using
CURLOPT_PROGRESSFUNCTION to implement your own timeout logic."
Feel free to contribute or just file an issue if you're interested.
[1]
https://curl.haxx.se/libcurl/c/CURLOPT_TIMEOUT.html
--
Thibault Nélis <
t...@osimis.io>
Osimis