Sets the account for an operation, if needed.

Transfers the file LocalFile to the remote server. If RemoteFile is specified, the name of the remote file that the file is appended to is set to RemoteFile, otherwise to LocalFile. If the file does not exists, it is created.

Transfers the binary Bin to the remote server and appends it to the file RemoteFile. If the file does not exist, it is created.

Transfers the chunk Bin to the remote server, which appends it to the file specified in the call to append_chunk_start/2.

For some errors, for example, file system full, it is necessary to call append_chunk_end to get the proper reason.

Starts the transfer of chunks for appending to the file RemoteFile at the remote server. If the file does not exist, it is created.

Stops transfer of chunks for appending to the remote server. The file at the remote server, specified in the call to append_chunk_start/2, is closed by the server.

Changes the working directory at the remote server to Dir.

Ends an FTP session, created using function open.

Deletes the file File at the remote server.

Given an error return value {error, AtomReason}, this function returns a readable string describing the error.

Changes the working directory to Dir for the local client.

Returns the current working directory at the local client.

Returns a list of files in long format.

Dir can be a directory or a file. The Dir string can contain wildcards.

ls/1 implies the current remote directory of the user.

The format of Listing depends on the operating system. On UNIX, it is typically produced from the output of the ls -l shell command.

Creates the directory Dir at the remote server.

Returns a list of files in short format.

Pathname can be a directory or a file. The Pathname string can contain wildcards.

nlist/1 implies the current remote directory of the user.

The format of Listing is a stream of filenames where each filename is separated by <CRLF> or <NL>. Contrary to function ls, the purpose of nlist is to enable a program to process filename information automatically.

Starts a FTP client process and opens a session with the FTP server at Host.

A session opened in this way is closed using function close.

The available configuration options are as follows:

{host, Host}

Host = string() | ip_address()

{port, Port}

Default is 0 which aliases to 21 or 990 when used with {tls_sec_method,ftps}).

{mode, Mode}

Default is passive.

{verbose, Verbose}

Determines if the FTP communication is to be verbose or not.

Default is false.

{debug, Debug}

Debugging using the dbg toolkit.

Default is disable.

{ipfamily, IpFamily}

With inet6fb4 the client behaves as before, that is, tries to use IPv6, and only if that does not work it uses IPv4).

Default is inet (IPv4).

{timeout, Timeout}

Connection time-out.

Default is 60000 (milliseconds).

{dtimeout, DTimeout}

Data connect time-out. The time the client waits for the server to connect to the data socket.

Default is infinity.

{tls, TLSOptions}

The FTP session is transported over tls (ftps, see RFC 4217). The list TLSOptions can be empty. The function ssl:connect/3 is used for securing both the control connection and the data sessions.

{tls_sec_method, TLSSecMethod}

When set to ftps will connect immediately with SSL instead of upgrading with STARTTLS. This suboption is ignored unless the suboption tls is also set.

Default is ftpes

{tls_ctrl_session_reuse, boolean()}

When set to true the client will re-use the TLS session from the control channel on the data channel as enforced by many FTP servers as (proposed and implemented first by vsftpd).

Default is false.

{sock_ctrl, SocketCtrls :: [SocketControl :: gen_tcp:option()]}

Passes options from SocketCtrls down to the underlying transport layer (tcp).

gen_tcp:option() except for ipv6_v6only, active, packet, mode, packet_size and header.

Default value is SocketCtrls = [].

{sock_data_act, [SocketControl]}

Passes options from [SocketControl] down to the underlying transport layer (tcp).

sock_data_act uses the value of sock_ctrl as default value.

{sock_data_pass, [SocketControl]}

Passes options from [SocketControl] down to the underlying transport layer (tcp).

sock_data_pass uses the value of sock_ctrl as default value.

{progress, Progress}

Progress = ignore | {Module, Function, InitialData}

Module = atom(), Function = atom()

InitialData = term()

Default is ignore.

Option progress is intended to be used by applications that want to create some type of progress report, such as a progress bar in a GUI. Default for the progress option is ignore, that is, the option is not used. When the progress option is specified, the following happens when ftp:send/[3,4] or ftp:recv/[3,4] are called:

• Before a file is transferred, the following call is made to indicate the start of the file transfer and how large the file is. The return value of the callback function is to be a new value for the UserProgressTerm that will be used as input the next time the callback function is called.

  Module:Function(InitialData, File, {file_size, FileSize})

• Every time a chunk of bytes is transferred the following call is made:

  Module:Function(UserProgressTerm, File, {transfer_size, TransferSize})

• At the end of the file the following call is made to indicate the end of the transfer:

  Module:Function(UserProgressTerm, File, {transfer_size, 0})

The callback function is to be defined as follows:

Module:Function(UserProgressTerm, File, Size) -> UserProgressTerm

UserProgressTerm = term()

File = string()

Size = {transfer_size, integer()} | {file_size, integer()} | {file_size, unknown}

For remote files, ftp cannot determine the file size in a platform independent way. In this case the size becomes unknown and it is left to the application to determine the size.

Note

The callback is made by a middleman process, hence the file transfer is not affected by the code in the progress callback function. If the callback crashes, this is detected by the FTP connection process, which then prints an info-report and goes on as if the progress option was set to ignore.

The file transfer type is set to the default of the FTP server when the session is opened. This is usually ASCII mode.

The current local working directory (compare lpwd/1) is set to the value reported by file:get_cwd/1, the wanted local directory.

The return value Pid is used as a reference to the newly created FTP client in all other functions, and they are to be called by the process that created the connection. The FTP client process monitors the process that created it and terminates if that process terminates.

Returns the current working directory at the remote server.

Transfers the file RemoteFileName from the remote server to the file system of the local client. If LocalFileName is specified, the local file will be LocalFileName, otherwise RemoteFileName.

If the file write fails, the command is aborted and {error, term()} is returned. However, the file is not removed.

Transfers the file RemoteFile from the remote server and receives it as a binary.

Starts transfer of the file RemoteFile from the remote server.

Receives a chunk of the remote file (RemoteFile of recv_chunk_start). The return values have the following meaning:

• ok = the transfer is complete.
• {ok, Bin} = just another chunk of the file.
• {error, Reason} = transfer failed.

Renames Old to New at the remote server.

Removes directory Dir at the remote server.

Transfers the file LocalFileName to the remote server. If RemoteFileName is specified, the name of the remote file is set to RemoteFileName, otherwise to LocalFileName.

Transfers the binary Bin into the file RemoteFile at the remote server.

Transfers the chunk Bin to the remote server, which writes it into the file specified in the call to send_chunk_start/2.

For some errors, for example, file system full, it is necessary to to call send_chunk_end to get the proper reason.

Starts transfer of chunks into the file RemoteFile at the remote server.

Stops transfer of chunks to the remote server. The file at the remote server, specified in the call to send_chunk_start/2 is closed by the server.

Dynamically starts an FTP session after the ftp application has been started.

Stops a started FTP session.

Sets the file transfer type to ascii or binary. When an FTP session is opened, the default transfer type of the server is used, most often ascii, which is default according to RFC 959.

Performs login of User with Pass.

Performs login of User with Pass to the account specified by Account.

Sends an arbitrary FTP command and returns verbatim a list of the lines sent back by the FTP server. This function is intended to give application accesses to FTP commands that are server-specific or that cannot be provided by this FTP client.