2023-01-02 20:51:48 +08:00
|
|
|
c: Copyright (C) Daniel Stenberg, <daniel@haxx.se>, et al.
|
2022-06-14 06:12:03 +08:00
|
|
|
SPDX-License-Identifier: curl
|
2016-11-16 06:44:58 +08:00
|
|
|
Long: max-time
|
|
|
|
Short: m
|
2021-08-31 22:37:14 +08:00
|
|
|
Arg: <fractional seconds>
|
|
|
|
Help: Maximum time allowed for transfer
|
2022-05-19 15:40:52 +08:00
|
|
|
See-also: connect-timeout retry-max-time
|
2020-07-13 20:15:04 +08:00
|
|
|
Category: connection
|
2021-08-31 22:37:14 +08:00
|
|
|
Example: --max-time 10 $URL
|
|
|
|
Example: --max-time 2.92 $URL
|
2021-09-28 17:50:07 +08:00
|
|
|
Added: 4.0
|
2022-10-18 16:39:43 +08:00
|
|
|
Multi: single
|
2016-11-16 06:44:58 +08:00
|
|
|
---
|
2022-05-19 15:40:52 +08:00
|
|
|
Maximum time in seconds that you allow each transfer to take. This is
|
2016-11-16 06:44:58 +08:00
|
|
|
useful for preventing your batch jobs from hanging for hours due to slow
|
|
|
|
networks or links going down. Since 7.32.0, this option accepts decimal
|
|
|
|
values, but the actual timeout will decrease in accuracy as the specified
|
|
|
|
timeout increases in decimal precision.
|
|
|
|
|
2022-05-19 15:40:52 +08:00
|
|
|
If you enable retrying the transfer (--retry) then the maximum time counter is
|
|
|
|
reset each time the transfer is retried. You can use --retry-max-time to limit
|
|
|
|
the retry time.
|
2022-11-23 18:24:26 +08:00
|
|
|
|
|
|
|
The decimal value needs to provided using a dot (.) as decimal separator - not
|
|
|
|
the local version even if it might be using another separator.
|