WebDAV
WebDAV extends HTTP with operations for working with files on a remote server. Mover can use a publicly reachable WebDAV server as a migration source or destination.
Connections
Create a new connection and select WebDAV as its type.
Provide a Connection Label so you can identify the connection in a list.
Server
Add the Hostname for your WebDAV server. The Hostname is a fully qualified domain name, not including any protocol prefix or path.
The default Port value of 443 is used for HTTPS. Only use an alternate port if the WebDAV server requires it. The other commonly used remote port, 80, typically means the server does not support SSL, in which case select http:// instead of https:// under protocol.
Indicate whether the Protocol for the connection is http:// or https://. The standard configuration uses https for the Protocol and 443 for the Port.
Authentication
Mover can authenticate with a username and password or a TLS client certificate.
Server Certificate
By default, Mover expects the WebDAV server certificate to match the connection hostname, be valid for the current date, and chain to a trusted certificate authority.
If the certificate does not meet those requirements, configure the connection to allow an untrusted certificate only after verifying the certificate and understanding the security tradeoff.
If you're not sure whether the server's certificate is fully valid, online tools are available for checking the validity of a site's certificate. The SSL Shopper SSL checker and the DigiCert SSL certificate checker are two options.
Case Sensitivity
Check how the source and destination handle letter case before starting a migration. On a case-sensitive system, MyFile.txt and myfile.txt can be two different files. A case-insensitive system treats those names as the same file.
Mover compares paths without regard to case or accents. When several source or destination items have the same case-insensitive name, Mover skips the duplicates and records the conflict in the run log. A single source file can overwrite a destination file whose name differs only by case when their reported sizes differ. Review the dry-run results and remove case-only duplicates before executing the migration.
Last updated
