bk99.de entertain the web since 1997

bk99.de
RFC · File transferStandard explained

RFC 959: FTP: File transfer with separate channels

Summary

RFC 959 describes FTP with separate control and data connections and stateful sessions. Separate channels made FTP flexible but make life hard for firewalls and NAT. The lack of transport encryption limits safe use today.

Ideas

  • Commands run over a persistent control channel.
  • File data uses a connection of its own.
  • Active and passive mode distribute connection setup differently.

Facts

  • RFC 959 replaces RFC 765.

Remarks

  • RFC 959 has the status “Internet Standard”; current errata and successor documents should also be checked.

Recommendations

  • Prefer SFTP or explicit FTPS for confidential data.
  • Use classic FTP only for deliberately public or historical counterparts.

References

Read the RFC at the RFC Editor

Search the Web Archive

Hackaday · 2026

Making FTP more bearable with modern command-line tools

Hackaday compares classic FTP clients with NcFTP for old servers, retro computers and unencrypted file transfers that are still necessary. FTP normally transmits credentials unencrypted. NcFTP has existed for many years.

Hostblogger · 2016

SFTP and FTPS as secure upload paths in web hosting

Manuel Schmitt points out that web hosting customers have been able to transfer files via SFTP or FTPS instead of unencrypted FTP for some time. On 26 October 2016, SFTP and FTPS had already been available for a while. Both methods were used for uploads to web hosting packages.

RFC · 2026

RFC 10008: HTTP QUERY: Safe, idempotent queries with content

RFC 10008 defines the HTTP method QUERY for complex, safe and idempotent queries with request content. New methods close gaps when established semantics do not fit cleanly. Explicit semantics are better than misused POST requests.