Mercurial > hgrepos > Python2 > PyMuPDF
comparison mupdf-source/thirdparty/curl/docs/cmdline-opts/ftp-method.d @ 3:2c135c81b16c
MERGE: upstream PyMuPDF 1.26.4 with MuPDF 1.26.7
| author | Franz Glasner <fzglas.hg@dom66.de> |
|---|---|
| date | Mon, 15 Sep 2025 11:44:09 +0200 |
| parents | b50eed0cc0ef |
| children |
comparison
equal
deleted
inserted
replaced
| 0:6015a75abc2d | 3:2c135c81b16c |
|---|---|
| 1 Long: ftp-method | |
| 2 Arg: <method> | |
| 3 Help: Control CWD usage | |
| 4 Protocols: FTP | |
| 5 Added: 7.15.1 | |
| 6 --- | |
| 7 Control what method curl should use to reach a file on an FTP(S) | |
| 8 server. The method argument should be one of the following alternatives: | |
| 9 .RS | |
| 10 .IP multicwd | |
| 11 curl does a single CWD operation for each path part in the given URL. For deep | |
| 12 hierarchies this means very many commands. This is how RFC 1738 says it should | |
| 13 be done. This is the default but the slowest behavior. | |
| 14 .IP nocwd | |
| 15 curl does no CWD at all. curl will do SIZE, RETR, STOR etc and give a full | |
| 16 path to the server for all these commands. This is the fastest behavior. | |
| 17 .IP singlecwd | |
| 18 curl does one CWD with the full target directory and then operates on the file | |
| 19 \&"normally" (like in the multicwd case). This is somewhat more standards | |
| 20 compliant than 'nocwd' but without the full penalty of 'multicwd'. | |
| 21 .RE |