RFC 3659:Extensions to FTP
RFC-Ref

validity


Click on the red underlined text to get to the source

... UTF-8 encoded Unicode string> raw = <any string that is not a valid UTF-8 encoding> ...
... NVFS is required to make sense of all possible pathnames. Server-PIs may restrict the syntax of valid pathnames in their NVFS in any manner appropriate to their implementation or underlying file system ...


... that a file has changed and that restarting a transfer would not give valid results. Note that this is applicable to any RESTart ...


... least one character. With the sole exception of the "/" character, any valid IS10646 character [10] may be used in a TVFS ...
... TVFS file or directory name is also a TVFS pathname. Such a pathname is valid to reference the file from the directory containing the name, that is, when that directory is the server-FTP ...
... Other TVFS pathnames are constructed by prefixing a pathname by a name of a directory from which the path is valid, and separating the two with the "/" character. Such a pathname is valid to reference ...
... name of a directory from which the path is valid, and separating the two with the "/" character. Such a pathname is valid to reference the file or directory from the directory containing the newly added directory name. ...
... root directory. Being unnamed, it cannot be represented in any other directory. A fully qualified pathname is valid to reference the named file or directory from any location (that is, regardless of what the current working directory ...
... current working directory of the server-FTP is a directory from which the relative pathname is valid. As a special case, the pathname "/" is defined to be a fully ...
... server-FTP is /A then the following pathnames, in addition to all the fully qualified pathnames, are valid C ...
... None of the following relative paths are valid when the current directory is /A ...
... Q Any of those could be made valid by changing the server-FTP's current working directory to the appropriate directory. Note that the paths ...
... current working directory to the appropriate directory. Note that the paths "P" and "Q" might refer to different files depending upon which directory is selected to cause those to become valid TVFS relative paths. ...


... TVFS is supported, any TVFS relative pathname valid in the current working directory, or any TVFS fully qualified pathname, may be given. If a ...
... requested operation. If the parameter is valid, then for an MLST command, the server-PI ...
... TVFS is supported, the name MAY be the fully qualified pathname of the directory, or MAY be any other pathname that is valid to refer to that directory from the current working directory of the server-FTP. Where more than one name ...


... The IETF takes no position regarding the validity or scope of any Intellectual Property Rights or other rights that might be claimed to ...



Google
Web
RFC-Ref