FTP Mode |
The mode to use when transferring or receiving files. Can
be either active, passive, extended active or extended
passive. If you experience problems with the data connection
you might try passive, since firewalls only allow passive
connections. When using passive (NOT extended passive) it
is possible to enable redirecting of the data part to
another system. This is however very uncommon and should
best be left disabled. |
Use LIST |
When AFD gets a an FTP directory listing it tries to get
the date and size by via the MLST command and if that
is not supported gets the information by sending the MDTM
and SIZE command for each file in the listing. On
connection with a high latency this can take a long
time. In this case you can set this option and AFD will
use the LIST command (ls -al) and try determine from
this output the date and size of each file. |
STAT |
The above LIST command has the disadvantage that it needs
a separate socket connection to send the data. Via the
the STAT command this is not required and the data is
send via existing control connection. Not all FTP
servers have this working correctly. So if you do
know the server does support it, enable this. |
Disable MLST |
Since AFD will try to automatically pick MLST when
the FTP server provides it, some of the implementations
are broken and can be disabled with this option. |
Send UTF8 on |
Some FTP servers need an 'OPTS UTF8 ON' for filenames
being created correctly. |
Clear Control Connection |
With FTPS it is always a problem to get it running
behind a firewall, because the firewall cannot read
which data port is going to be opened for transmitting
the data, since the control connection is encrypted.
When this option is set AFD will drop encryption
by sending the CCC command, after having logged in
successfully. |
Implicit |
This sets implicit FTPS. If not set explicit FTPS
is used which is also the default. |
Set idle time |
The idle time will be set to the value that is set in the
Transfer timeout field. Note not all FTP servers support
this. |
STAT Keepalive |
Some firewalls timeout the control connection when there
is no activity on it. This can happen transferring large
files over a slow connection. This option, if set, will
send keepalive commands over the control connection
during transfer. Most FTP servers do not support this
(only vsftpd does support indirectly). |
Fast rename |
This will send the RNFR (rename from) and RNTO (rename to)
commands in one go, not as two separate commands. It reduces
latency of renaming, but note that some FTP-servers do not
support this, especially those from M$soft. |
Fast cd |
If set no CWD (change working directory) command is sent. This
reduces latency, but does not always work (eg. VAX systems). |
Ignore type I |
By default AFD will always send a type I command for
binary mode during connection initialization. Since some
FTP-servers have this set by default, it is not required
to send this. Note however that this option is very
dangerous and only works with few FTP-servers (vsftpd),
it can easily corrupt data, because some FTP-servers use
ASCII mode as default. |
Allow burst |
AFD by default tries to append a new job to an existing
sending job, to reduce the number of connections and the
overall latency. It can however happen that some servers
have problems with this. So with this option it is possible
to disable bursting. |
TCP Keepalive |
Sets the keepalive flag for the TCP connection. When the
keepalive option is set and no data has been exchanged in
either direction for 2 hours, TCP automatically sends a
keepalive probe. If the system does support the socket()
option TCP_KEEPALIVE, then the timeout value is set to
that value entered in the 'Tansfer timeout' field minus
5 seconds and not the default 2 hours. |
Bucketname in path |
For AWS4 HTTP one needs to set this if the bucketname
is at the first element of the path entry. If the bucketname
is in the hostname one does not need to set this option. |
No expect |
When sending a file via HTTP one can send a
"Expect: 100-continue". This makes it easier to transmit
large files. It is set by default. Some servers do not
handle this correctly or do not know this option. So
here you can disable it. |
Seq. Locking |
When transmitting file "xxxx.yyyy" it adds the number of
retries to the end of the file name "xxxx.yyyy-"
during transmission. After the file was transmitted
successful it is renamed to the original name "xxxx.yyyy".
Note, when set appending will NOT be possible. This option
is useful when the remote side has problems with still having
this file open by some other process, since with every try
it will open a new file with a different name. It will try to
delete the previous before it opens a new one. This option
can be combined with the other locking options.
|
Compression |
If the protocol does support compression enable this
to reduce the volume send to this host. This does increase
the CPU time used and not all data does compress well.
This can currently only be enabled for protocol SCP and
SFTP. |
Strict Host Key |
For SSH, that is SFTP and SCP, strict host key checking
can be disabled via this option. Do not unset this
option unless you really know what you are doing. |
Keep time stamp |
This tries to preserve the original time stamp of the
file being transmitted. Currently this only works
with FTP, FILE and SFTP. |
Sort file names |
Files are being sorted by their name before being send. |
No ageing |
When during transmission an error occurs, the job with this
error starts to age. This means its priority decreases so much
that even jobs that have a lower priority become more important
and can bypass an error job. If you set this button it
will no longer do this. |
Match size |
After file is transmitted check the size of the destination
file with that of the local file just send. If they do not
match, show an error and then resend the file. |
Strict TLS |
Checks if the server provides a valid certificate. |
Legacy renegotiation |
Some combination of openssl and HTTP servers need this
set to successfully connect. By default tis is off. |