mirror of
https://github.com/curl/curl.git
synced 2024-12-21 06:50:10 +08:00
3e33681eaf
- "FTP with CONNECT and slow server" I believe this is not a problem these days. - "FTP with NULs in URL parts" The FTP protocol does not support them properly anyway. - remove "FTP and empty path parts in the URL" I don't think this has ever been reported as a real problem but was only a hypothetical one. - "Premature transfer end but healthy control channel" This is not a bug, this is an optimization that *could* be performed but is not an actual problem. - "FTP without or slow 220 response" Instead add to the documentation of the connect timeout that the connection is considered complete at TCP/TLS/QUIC layer. Closes #9979
23 lines
829 B
Makefile
23 lines
829 B
Makefile
c: Copyright (C) 1998 - 2022, Daniel Stenberg, <daniel@haxx.se>, et al.
|
|
SPDX-License-Identifier: curl
|
|
Long: connect-timeout
|
|
Arg: <fractional seconds>
|
|
Help: Maximum time allowed for connection
|
|
See-also: max-time
|
|
Category: connection
|
|
Example: --connect-timeout 20 $URL
|
|
Example: --connect-timeout 3.14 $URL
|
|
Added: 7.7
|
|
Multi: single
|
|
---
|
|
Maximum time in seconds that you allow curl's connection to take. This only
|
|
limits the connection phase, so if curl connects within the given period it
|
|
will continue - if not it will exit. Since version 7.32.0, this option
|
|
accepts decimal values.
|
|
|
|
The "connection phase" is considered complete when the requested TCP, TLS or
|
|
QUIC handshakes are done.
|
|
|
|
The decimal value needs to provided using a dot (.) as decimal separator - not
|
|
the local version even if it might be using another separator.
|