| xf.li | 6c8fc1e | 2023-08-12 00:11:09 -0700 | [diff] [blame] | 1 | c: Copyright (C) 1998 - 2022, Daniel Stenberg, <daniel@haxx.se>, et al. |
| 2 | SPDX-License-Identifier: curl |
| 3 | Long: ftp-method |
| 4 | Arg: <method> |
| 5 | Help: Control CWD usage |
| 6 | Protocols: FTP |
| 7 | Added: 7.15.1 |
| 8 | Category: ftp |
| 9 | Example: --ftp-method multicwd ftp://example.com/dir1/dir2/file |
| 10 | Example: --ftp-method nocwd ftp://example.com/dir1/dir2/file |
| 11 | Example: --ftp-method singlecwd ftp://example.com/dir1/dir2/file |
| 12 | See-also: list-only |
| 13 | Multi: single |
| 14 | --- |
| 15 | Control what method curl should use to reach a file on an FTP(S) |
| 16 | server. The method argument should be one of the following alternatives: |
| 17 | .RS |
| 18 | .IP multicwd |
| 19 | curl does a single CWD operation for each path part in the given URL. For deep |
| 20 | hierarchies this means many commands. This is how RFC 1738 says it should |
| 21 | be done. This is the default but the slowest behavior. |
| 22 | .IP nocwd |
| 23 | curl does no CWD at all. curl will do SIZE, RETR, STOR etc and give a full |
| 24 | path to the server for all these commands. This is the fastest behavior. |
| 25 | .IP singlecwd |
| 26 | curl does one CWD with the full target directory and then operates on the file |
| 27 | "normally" (like in the multicwd case). This is somewhat more standards |
| 28 | compliant than 'nocwd' but without the full penalty of 'multicwd'. |
| 29 | .RE |