| ascp: Transferring from the Command Line with Ascp |
113
Note:
If you are authenticating on a Windows computer as a domain user, the transfer server
strips the domain from the username. For example,
Administrator
is authenticated rather than
DOMAIN\Administrator
. For this reason, you must specify the domain explicitly.
-v
Run
ascp
in verbose mode. This option prints connection and authentication debug messages in the
log file. For information on log files, see
on page 348 .
-W
{
token_string
|@
token_file
}
Authenticate using the authorization token string for the transfer, either as the string itself or when
preceded with an
@
, the full path to the token file. This option takes precedence over the setting for
the
ASPERA_SCP_TOKEN
environment variable.
-wr
,
-wf
Measure and report bandwidth from server to client (
-wr
) or client to server (
-wf
) before the
transfer.
-X
rexmsg_size
Limit the size of retransmission requests to no larger than the specified size, in bytes. (Max: 1440)
-Z
dgram_size
Use the specified datagram size (MTU) for FASP transfers. Range: 296-65535 bytes. (Default: the
detected path MTU)
As of version 3.3, datagram size can be specified on the server by setting
<datagram_size>
in
aspera.conf
. The server setting overrides the client setting, unless the client is using a version
of
ascp
that is older than 3.3, in which case the client setting is used. If the pre-3.3 client does not
set
-Z
, the datagram size is the discovered MTU and the server logs the message "LOG Peer client
does not support alternative datagram size".
Ascp Options for HTTP Fallback
HTTP fallback serves as a secondary transfer method when the Internet connectivity required for Aspera FASP
transfers (UDP port 33001, by default) is unavailable. When HTTP fallback is enabled and UDP connectivity is lost
or cannot be established, the transfer will continue over the HTTP/S protocol.
Limitations:
• HTTP fallback must be enabled on the server.
• Folders that are symbolic links cannot be downloaded directly by using HTTP fallback. Folders that are symbolic
links are processed correctly when their parent folder is the source.
• HTTP fallback can only follow symbolic links. Settings in
aspera.conf
or in the command line are ignored.
• HTTP fallback attempts to transfer at the target rate but is limited by TCP.
• HTTP fallback does not support pre-post processing or inline validation.
Options:
-I
cert_file
Certify fallback transfers with the specified HTTPS certificate file.
-j {0|1}
Encode all HTTP transfers as JPEG files when set to 1. (Default: 0)
-t
port
Transfer via the specified server port for HTTP fallback.
-x
proxy_server
Transfer to the specified proxy server address for HTTP fallback.
-Y
key_file
Certify HTTPS fallback transfers using the specified HTTPS transfer key.
