Protocol reference

Use this page to check compatibility before choosing a server or investigating a transfer limitation. For connection steps, see FTP, FTPS, SFTP or WebDAV.

On this page

Capabilities

Capability FTP FTPS SFTP WebDAV
Transport protection None Explicit TLS SSH HTTPS when using https://
Server identity None Certificate Pinned host key Certificate with HTTPS
Browse, create folders, rename and delete Yes Yes Yes Yes
Upload and download Yes Yes Yes Yes
Resume a download Conditional Conditional Conditional Conditional
Resume an upload Conditional Conditional Conditional No
Copy between connections Yes Yes Yes Yes
Move within one connection Yes Yes Yes Yes

“Conditional” means the saved partial and the source must pass the checks below. Server permissions, storage quotas and supported operations can restrict what an account can do. Copying between connections relays the data through your computer. Moving between different connections, or between a server and your computer, is refused; copy instead.

Authentication and transport

FTP and explicit FTPS use a username and password. FTPS starts TLS after the FTP greeting; implicit FTPS, which starts TLS immediately, is not supported. FTP itself sends credentials and data without encryption.

FTPS supports TLS 1.2 and TLS 1.3. Keep certificate verification enabled. For an organisation's own certificate authority, select its CA file rather than turning verification off. See FTPS certificates.

SFTP supports password and SSH private-key login. The OpenSSH key loader is tested with Ed25519, RSA and ECDSA P-256 keys, with and without a passphrase. These are key-file checks, not a promise that every server accepts each key. See SFTP keys and fingerprints.

If password authentication is refused, SFTP can fall back to keyboard-interactive authentication, answering hidden prompts with the saved password. This is not an interactive one-time-code prompt.

WebDAV uses Basic authentication, not Digest. Use an HTTPS endpoint. A server that accepts only Digest refuses sign-in. The URL must have no embedded credentials, query string or fragment. Plain HTTP requires an explicit opt-in before credentials are sent; a same-host, same-path redirect can upgrade it to HTTPS. See WebDAV connections.

SSH algorithms

These are the SSH library's default offers, in preference order. The server and client must agree on algorithms; this table does not mean every combination has been tested against every server. Host-key algorithms identify the server and are separate from the format of your private-key file.

SSH category Default offer, in order
Key exchange mlkem768x25519-sha256, curve25519-sha256, curve25519-sha256@libssh.org, diffie-hellman-group-exchange-sha256, diffie-hellman-group18-sha512, diffie-hellman-group17-sha512, diffie-hellman-group16-sha512, diffie-hellman-group15-sha512, diffie-hellman-group14-sha256
Host key ssh-ed25519, ecdsa-sha2-nistp256, ecdsa-sha2-nistp384, ecdsa-sha2-nistp521, rsa-sha2-512, rsa-sha2-256, ssh-rsa
Cipher chacha20-poly1305@openssh.com, aes256-gcm@openssh.com, aes256-ctr, aes192-ctr, aes128-ctr
MAC hmac-sha2-512-etm@openssh.com, hmac-sha2-256-etm@openssh.com, hmac-sha2-512, hmac-sha2-256
Compression none, zlib, zlib@openssh.com

SSH negotiation extension markers are omitted. Host-key certificates are not in the default offer. With the default host-key checking, an unconfirmed key stops login until you trust its fingerprint; verify it with the administrator. A changed pinned key stops the connection.

Resume and integrity

Downloads are written to a hidden sibling .ftpeach-<id>.part file. Resume requires the same endpoint, remote path, size and recorded version. Changed or unknown source information starts a fresh download. The partial replaces the destination only after its size is verified; a short download keeps the previous destination intact.

WebDAV resumes with a Range request and validates the returned range. If the server ignores Range, the download restarts. A version read in the same second as the modification is not trusted for resume.

Paused FTP/FTPS and SFTP uploads resume only if the local source identity still matches and up to 8 KiB of the retained staging tail matches the source. Changed or unverifiable staging restarts the upload. This is not a full hash of everything already sent. WebDAV uploads offer no Pause and start over on retry. See Transfers for the controls.

Limitations

FTP/FTPS and SFTP identify remote versions by size and modification time, with one-second time resolution. Replacing a file with different content of the same size within that second can escape this check. If a file is being rewritten, download it again from the start instead of resuming it.

FTP active mode needs the server to connect back to your computer and is disabled when using a proxy. SOCKS4/4a cannot address IPv6 destinations; SOCKS5 and HTTP CONNECT can. See FTP data connections and networking details for proxy configuration.

Compatibility verification

Automated checks cover local protocol servers, authentication, certificate and host-key rejection, transfers and resume. The SSH algorithm table is checked against the dependency's defaults so a library update cannot silently leave it stale. For the broader release checks against server implementations and faulty links, see How releases are verified.

Read this page on GitHub

Swipe to explore the enlarged image.