FTP Client Test 0.5

Graphic interface (using the Treeview widget) for viewing directory contents. It is still fairly rough - so be gentle (for example, if you open a sub-folder, wait for its contents to display before opening another folder; If you try and retrieve a file, the results will be output to the terminal window only).

Note you can also send raw ftp commands via the terminal. Please note that this Shockwave movie is very beta and may not be very well behaved with your ftp server. Please use with caution.

Launch FTP Client in Window (~87k)

Some useful commands to try:

  • HELP - lists commands supported by the server
  • STAT - cause a status response to be sent over the control connection in the form of a reply
  • PASV - switches to passive mode and opens a connection on the port specified by the server. Note that you must precede some commands (such as LIST, NLST etc) with PASV or PORT commands. The opening of the server-specified port is handled automatically when the FTP_Session script receives the appropriate server reply on the control port.
  • LIST - causes a list to be sent from the server to the passive DTP. Must be preceeded by a PORT or PASV command.
  • NLST - causes a directory listing to be sent from server to user site. Must be preceeded by a PORT or PASV command.
  • ABOR - abort the previous FTP service command and any associated transfer of data
  • PWD - prints current working directory
  • CWD - change working directory
  • RETR - note that the results are simply put into a field (so dont try and download a large binary file). Must be preceeded by a PORT or PASV command.
  • NOOP - does not affect any parameters or previously entered commands. It specifies no action other than that the server send an OK reply
  • MKD - make a directory
  • SYST - Prints the type of operating system at the server.

Some simple wrapper script for returning a directory list (in a lingo list format) will be available on Lingoworkshop soon.

Related Info

More information on the RFC 959 File Transfer Protocol can be found here.

First published 15/06/2005