FEAT
Click on the red underlined text to get to the source
... in responses. When the MLST command is supported, as indicated in
the response to the FEAT command [6], pathnames are to be transferred
in one of the following two formats.
...
... FEAT Response for SIZE ...
... case. That is, the response SHOULD be:
C> FEAT
S> 211- <any descriptive text>
S> ...
...
... RESTart in STREAM mode, as
specified here, it MUST include, in the response to the FEAT command
[6], a line containing exactly the string "REST ...
... REST is not supported at all or supported only in block or
compressed modes, the REST line MUST NOT be included in the FEAT
response. Where required, the response SHOULD be:
...
... upper case is not required). Servers SHOULD send upper case.
Such a response to the FEAT command MUST NOT be returned unless the
server implements TVFS as defined here.
...
... defined characters, and simply ignore it if unrecognized.
A typical response to the FEAT command issued by a server
implementing only this specification would be:
...
...
The initial space shown in the mlst-feat response is that required by
the FEAT command, two spaces are not permitted. If no factlist is
given, then the server-FTP process is indicating that it supports
...
... MLST format responses, until an "OPTS MLST" is given to
alter the list of facts returned. After that, subsequent FEAT
commands will return the asterisk to show the facts selected by the
most recent "OPTS MLST".
...
... be included, the list of facts will be empty. Note that the list of
facts returned will be the same as those marked by a trailing
asterisk ("*") in a subsequent FEAT command response. There is no
requirement that the order of the facts returned be the same as that
...
... requirement that the order of the facts returned be the same as that
in which they were requested, or that in which they will be listed in
a FEAT command response, or that in which facts are returned in MLST
responses. The fixed string "MLST ...
... then changed by the client. The first change shows facts that are
available from the server being selected. Subsequent FEAT output
shows the altered features as being returned. The client then
...
... attempts to select some standard features that the server does not
support. This is not an error, however the server simply ignores the
requests for unsupported features, as the FEAT output that follows
shows. Then, the client attempts to request a non-standard, and
...
... value of the unique fact.
The FEAT and OPTS commands may be issued before the FTP
authentication ...