REST
Click on the red underlined text to get to the source
... MLST", and "MLSD". The existing
command "REST" is modified. Of those, the "SIZE" and "MDTM"
commands, and the modifications to "REST ...
... REST" is modified. Of those, the "SIZE" and "MDTM"
commands, and the modifications to "REST" have been in wide use for
many years. The others are new.
...
... NVFS was last modified. This command has
existed in many FTP servers for many years, as an adjunct to the REST
command for STREAM mode, thus is widely available. However, where
...
... conjunction with
the RESTART (REST) command when STORing a file to a remote server in
STREAM mode, to determine the restart ...
... unavailable, or some other error has occurred. The value returned is
in a format suitable for use with the RESTART (REST) command for mode
STREAM, provided the transfer mode and type are not altered.
...
... Restart of Interrupted Transfer (REST) ...
... itself. This is done by using the SIZE command, if needed, in
combination with the RESTART (REST) command, and one of the standard
file transfer commands.
...
... 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 parameter has been saved, and
...
... server-PI will respond to the REST command with a
350 reply, indicating that the REST parameter has been saved, and
that another command, which should be either RETR or STOR ...
... restart marker value.
The REST command is intended to complete a failed transfer. Use with
RETR is comparatively well defined in all cases, as the client ...
... data into the file named. The results are undefined if a client uses
REST to do other than restart to complete a transfer of a file that
had previously failed to completely transfer. In particular, if the
...
... had previously failed to completely transfer. In particular, if the
restart marker set with a REST command is not at the end of the data
currently stored at the server, as reported by the server, or if
...
... by the server, or if
insufficient data are provided in a STOR that follows a REST to
extend the destination file to at least its previous size, then the
...
... effects are undefined.
The REST command must be the last command issued before the data
transfer command that is to cause a restarted, rather than a
complete, file transfer ...
... data
transfer command that is to cause a restarted, rather than a
complete, file transfer. The effect of issuing a REST command at any
other time is undefined. The server-PI may react to a badly
...
... other time is undefined. The server-PI may react to a badly
positioned REST command by issuing an error response to the following
command, not being a restartable data transfer ...
... restart attempt.
Because of this, a user-PI that has issued a REST command, but that
has not successfully transmitted the following data transfer command
...
... has not successfully transmitted the following data transfer command
for any reason, should send another REST command before the next data
transfer command. If that transfer is not to be restarted, then
"REST ...
... REST command before the next data
transfer command. If that transfer is not to be restarted, then
"REST 0" should be issued.
An error response ...
...
An error response will follow a REST command only when the server
does not implement the command, or when the restart marker value is
...
... syntactically invalid for the current transfer mode (e.g., in STREAM
mode, something other than one or more digits appears in the
parameter to the REST command). Any other errors, including such
problems as restart marker out of range ...
... FEAT command
[6], a line containing exactly the string "REST STREAM". This string
is not case sensitive, but it SHOULD be transmitted in upper case.
...
... STREAM". This string
is not case sensitive, but it SHOULD be transmitted in upper case.
Where REST is not supported at all or supported only in block or
compressed modes, the REST line MUST NOT be included in the FEAT ...
... Where 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:
...
... REST Example ...
... S> 200 PORT command successful.
C> REST 802816
S> 350 Restarting at 802816. Send STORE or RETRIEVE
...
... 4. The most common need for this accuracy is likely to be in
conjunction with the REST command described in section 5. The size
fact, on the other hand, should be used for purposes such as
indicating to a human user ...
... Apologies are offered to any inadvertently omitted.
The description of the modifications to the REST command and the MDTM
and SIZE commands comes from a set of modifications suggested for STD ...