Lines Matching refs:FTP
288 protocol data as well (especially when using FTP). If you are using HTTP,
310 uploading to a remote FTP site is similar to uploading data to an HTTP server
387 There is a long time Unix "standard" way of storing FTP usernames and
395 non-FTP protocols such as HTTP. To make curl use this file, use the
836 use the HTTP protocol. For example, you cannot invoke your own custom FTP
837 commands or even proper FTP directory listings.
867 named 'ftp_proxy' is checked for FTP URLs. Again, the proxies are always HTTP
916 operations over an HTTP proxy. You can in fact use things such as FTP
917 upload or FTP custom commands this way.
969 FTP connections that are kept alive save a lot of time, as the command-
971 without permission to login again like on many FTP servers only allowing N
1022 programming you may need to change the traditional HTTP (or FTP or...)
1101 ## FTP Custom Commands
1104 you want to make, for example, your FTP transfers to behave differently.
1106 Sending custom commands to an FTP server means that you need to send the
1107 commands exactly as the FTP server expects them (RFC 959 is a good guide
1134 The custom FTP commands are issued to the server in the same order they are
1145 The option to enable headers or to run custom FTP commands may be useful to
1149 ## FTP Custom CURLOPT_CUSTOMREQUEST
1151 If you do want to list the contents of an FTP directory using your own defined
1152 FTP command, CURLOPT_CUSTOMREQUEST(3) does just that. "NLST" is the default
1210 # FTP Peculiarities We Need
1212 FTP transfers use a second TCP/IP connection for the data transfer. This is
1222 work it tries PASV instead. (EPSV is an extension to the original FTP spec
1223 and does not exist nor work on all FTP servers.)
1336 "Headers" for FTP transfers equal all the FTP server responses. They are not
