Question
So far I couldn't find anything really, but is it true that curl doesn't really time out at all?
Will curl always wait (or is it depending on configuration) or is there any sort of timeout?
How-To
curl has two options: --connect-timeout and --max-time. Quoting from the manpage:
- --connect-timeout
- Maximum time in seconds that you allow the connection to the
- server to take. This only limits the connection phase, once
- curl has connected this option is of no more use. Since 7.32.0,
- this option accepts decimal values, but the actual timeout will
- decrease in accuracy as the specified timeout increases in deci‐
- mal precision. See also the -m, --max-time option.
- If this option is used several times, the last one will be used.
- -m, --max-time
- Maximum time in seconds that you allow the whole operation to
- take. This is useful for preventing your batch jobs from hang‐
- ing for hours due to slow networks or links going down. Since
- 7.32.0, this option accepts decimal values, but the actual time‐
- out will decrease in accuracy as the specified timeout increases
- in decimal precision. See also the --connect-timeout option.
- If this option is used several times, the last one will be used.
Here (on Debian) it stops trying to connect after 2 minutes, regardless of the time specified with --connect-timeout and although the default connect timeout value seems to be 5 minutes according to the DEFAULT_CONNECT_TIMEOUT macro in lib/connect.h. A default value for --max-time doesn't seem to exist, making curl wait forever for a response if the initial connect succeeds.
What to use?
You are probably interested in the latter option, --max-time. For your case set it to 900 (15 minutes).
Specifying option --connect-timeout to something like 60 (one minute) might also be a good idea. Otherwise curl will try to connect again and again, apparently using some backoff algorithm.
沒有留言:
張貼留言