PI
Click on the red underlined text to get to the source
... DTP" (data transfer
process), "user-FTP process", "user-PI" (user protocol interpreter),
"user-DTP", "server-FTP process ...
... UTF-8 encoding>
Which format is used is at the option of the user-PI or server-PI
sending the pathname. UTF-8 ...
...
Which format is used is at the option of the user-PI or server-PI
sending the pathname. UTF-8 encodings ...
... UTF-8 or raw encoding has been used, in those cases where
it matters. While it is useful for the user-PI to be able to
correctly display a pathname received from the server-PI to the user,
...
... it matters. While it is useful for the user-PI to be able to
correctly display a pathname received from the server-PI to the user,
it is far more important for the user-PI to be able to retain and
...
... correctly display a pathname received from the server-PI to the user,
it is far more important for the user-PI to be able to retain and
retransmit the identical pathname when required. Implementations are
advised against converting a UTF-8 ...
... created. This does not imply that the
NVFS is required to make sense of all possible pathnames. Server-PIs
may restrict the syntax of valid pathnames in their NVFS ...
... manner appropriate to their implementation or underlying file system.
Similarly, a server-PI may parse the pathname and assign meaning to
the components detected.
...
... calendar regardless of what calendar may have been in use at the date
and time indicated at the location of the server-PI.
The technical differences among GMT ...
... Section 4.2 of [3] defines the format and meaning of replies by the
server-PI to FTP commands from the user-PI. Those reply conventions
...
... by the
server-PI to FTP commands from the user-PI. Those reply conventions
are used here without change.
...
... digit code that is their first element. Thus the term "500 reply"
means a reply from the server-PI using the three digit code "500".
...
... FTP dialogs presented in this document, lines that
begin "C> " were sent over the control connection from the user-PI to
the server-PI, lines that begin "S> " were sent over the control
connection ...
... control connection from the user-PI to
the server-PI, lines that begin "S> " were sent over the control
connection from the server-PI to the user-PI ...
... the server-PI, lines that begin "S> " were sent over the control
connection from the server-PI to the user-PI, and each sequence of
lines that begin "D> " was sent from the server-PI ...
... server-PI, lines that begin "S> " were sent over the control
connection from the server-PI to the user-PI, and each sequence of
lines that begin "D> " was sent from the server-PI to the user-PI ...
... server-PI to the user-PI, and each sequence of
lines that begin "D> " was sent from the server-PI to the user-PI
over a data connection ...
... user-PI, and each sequence of
lines that begin "D> " was sent from the server-PI to the user-PI
over a data connection created ...
... positive response carrying a time-val
with an unspecified value, the choice being made by the server-PI.
The server-PI ...
... PI.
The server-PI will respond to the MDTM command with a 213 reply
giving the last modification time ...
... files at all, then the MDTM command may behave as indicated. The
"C>" lines are commands from user-PI to server-PI, the "S>" lines are
server-PI ...
... MDTM command may behave as indicated. The
"C>" lines are commands from user-PI to server-PI, the "S>" lines are
server-PI replies.
...
... STREAM mode, to determine the restart point. The server-PI might
need to read the partially transferred file, do any appropriate
conversion, and count the number of octets that would be generated
...
... CRLF
The server-PI will respond to the SIZE command with a 213 reply
giving the transfer size of the file whose pathname was supplied, or
an error response ...
...
Since calculating the size of a file with this degree of precision
may take considerable effort on the part of the server-PI, user-PIs
should not used this command unless this precision is essential (such
...
... Since calculating the size of a file with this degree of precision
may take considerable effort on the part of the server-PI, user-PIs
should not used this command unless this precision is essential (such
as when about to restart ...
... effectively disables restart, causing the entire file to be
transmitted. The server-PI will respond to the REST command with a
350 reply, indicating that the REST ...
... file transfer. The effect of issuing a REST command at any
other time is undefined. The server-PI may react to a badly
positioned REST command by issuing an error response ...
... command, or it may silently ignore the inappropriate restart attempt.
Because of this, a user-PI that has issued a REST command, but that
has not successfully transmitted the following data transfer ...
... contain the character "/". Where the underlying natural file store
permits files, or directories, to contain the "/" character in their
names, a server-PI implementing TVFS must encode that character in
some manner whenever file or directory names are being returned to
...
... TVFS must encode that character in
some manner whenever file or directory names are being returned to
the user-PI, and reverse that encoding whenever such names are being
accepted from the user-PI ...
... user-PI, and reverse that encoding whenever such names are being
accepted from the user-PI.
The encoding ...
... itself. For these purposes, the contents of a directory are whatever
file or directory names (not pathnames) the server-PI will allow to
be referenced when the current working directory is the directory
...
... be referenced when the current working directory is the directory
named, and which the server-PI desires to reveal to the user-PI.
Note that omitting the argument is the only defined way to obtain a
...
... current working directory is the directory
named, and which the server-PI desires to reveal to the user-PI.
Note that omitting the argument is the only defined way to obtain a
listing of the current directory, unless a pathname that represents
...
... the directory happens to be known. In particular, there is no
defined shorthand name for the current directory. This does not
prohibit any particular server-PI implementing such a shorthand.
No title, header ...
... If the parameter is valid, then for an MLST command, the server-PI
will send the first (leading) line of the control response, the entry
for the pathname given, or the current directory if no pathname was
...
... relevant information about the file named on the same line, and they
are in the set requested by the user-PI. See section 7.9 (page 51).
There is no requirement that the same set of facts be provided for
...
... TVFS path naming the same file. Where no argument
was given to the MLST command, the server-PI may either include an
empty file name in the response, or it may supply a name that refers
to the current directory, if such a name is available. Where TVFS ...
...
When TVFS is supported, a user-PI can refer to any file or directory
in the listing by combining a type "cdir" name, with the appropriate
name from the directory listing using the procedure defined in
...
... start, though frequently may do so, and may occur
multiple times. It MUST NOT be included if the type fact is not
included, or there would be no way for the user-PI to distinguish the
name of the directory from an entry in the directory.
...
... returned in the same MLSD output (see section 6.2). These pathnames
are only expected to work when the server-PI's position in the NVFS
file tree ...
... semantics associated
with a "type=cdir" entry are that, provided the current working
directory of the server-PI has not been changed, a pathname of type
"cdir" may be used as an argument to a CWD command, which will cause
...
... "cdir" may be used as an argument to a CWD command, which will cause
the current directory of the server-PI to change so that the
directory that was listed in its current working directory.
...
... pathname, or a fully qualified pathname. A relative pathname will be
relative to the directory being listed, not to the current directory
of the server-PI at the time.
For the purposes of this type value ...
... fact (see immediately following section) containing the same value,
indicating that the same file is represented by all such names.
User-PIs transferring the file need then transfer it only once, and
then insert their own form of indirect reference to construct
alternate names where desired, or perhaps even copy the local file if
...
...
Where a file is such that it may validly, and sensibly, treated by
the server-PI as being of more than one of the above types, then
multiple entries should be returned, each with its own "Type" fact of
the appropriate type, and each containing the same pathname. This
...
... the appropriate type, and each containing the same pathname. This
may occur, for example, with a structured file, which may contain
sub-files, and where the server-PI permits the structured file to be
treated as a unit, or treated as a directory allowing the sub-files
...
... is made to a file such that the results of a RETR command would
differ, then the value of the modify fact should alter. User-PIs
should not assume that a different modify fact value indicates that
the file contents are necessarily different than when last retrieved.
...
...
By using an system dependent fact, or a local fact, a server-PI may
communicate to the user-PI information about the file named that is
...
... By using an system dependent fact, or a local fact, a server-PI may
communicate to the user-PI information about the file named that is
peculiar to the underlying file system.
...
... choosing. As the method of interpretation of such information will
generally not be widely understood, server-PIs should be aware that
clients will typically ignore any local facts provided. As there is
...
... registration of locally defined facts, it is entirely possible
that different servers will use the same local fact name to provide
vastly different information. Hence user-PIs should be hesitant
about making any use of any information in a locally defined fact
without some other specific assurance that the particular fact is one
...
... manner best suited for the particular user. Explanatory text in
responses generally has no particular meaning to the protocol. The
numeric codes provide all necessary information. Server-PIs are free
to provide the text in any language that can be adequately
...