Connected: An Internet Encyclopedia
4.1.2.7 LIST and NLST Commands: RFC-959 Section 4.1.3

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1123
Up: 4. FILE TRANSFER
Up: 4.1 FILE TRANSFER PROTOCOL -- FTP
Up: 4.1.2. PROTOCOL WALK-THROUGH
Prev: 4.1.2.6 PASV Command: RFC-959 Section 4.1.2
Next: 4.1.2.8 SITE Command: RFC-959 Section 4.1.3

4.1.2.7 LIST and NLST Commands: RFC-959 Section 4.1.3

4.1.2.7 LIST and NLST Commands: RFC-959 Section 4.1.3

The data returned by an NLST command MUST contain only a simple list of legal pathnames, such that the server can use them directly as the arguments of subsequent data transfer commands for the individual files.

The data returned by a LIST or NLST command SHOULD use an implied TYPE AN, unless the current type is EBCDIC, in which case an implied TYPE EN SHOULD be used.

DISCUSSION:

Many FTP clients support macro-commands that will get or put files matching a wildcard specification, using NLST to obtain a list of pathnames. The expansion of "multiple-put" is local to the client, but "multiple- get" requires cooperation by the server.

The implied type for LIST and NLST is designed to provide compatibility with existing User-FTPs, and in particular with multiple-get commands.


Next: 4.1.2.8 SITE Command: RFC-959 Section 4.1.3

Connected: An Internet Encyclopedia
4.1.2.7 LIST and NLST Commands: RFC-959 Section 4.1.3