WebDAV (Outbound to a Remote)
Connect a partner's or your organization's WebDAV service when Files.com needs to read or deliver its files over HTTP-based file access. A Mount exposes the remote working files through Files.com; a Sync delivers a separate copy between locations. For applications connecting into Files.com, use the inbound WebDAV guidance.
Use HTTPS to encrypt the connection. If the same remote service also offers FTPS, we recommend FTPS when outbound transfer speed is the priority. Compare representative transfers against the actual service when choosing: file sizes, request latency, and server capacity affect the result. WebDAV fits services whose supported access method is WebDAV and workloads that perform adequately through it.
Connection Details
Select WebDAV when adding a Remote Server. The connection authenticates with a username and password, entered directly or selected from the Remote Server Credential Manager.
| Setting | Requirement |
|---|---|
| Hostname | A fully qualified domain name, without a protocol prefix or folder path. It must be resolvable and reachable from the selected connection route. |
| Protocol | https:// for encrypted access. http:// sends credentials and file contents without encryption. |
| Port | Normally 443 for HTTPS or 80 for HTTP; use the port specified by the remote operator. |
If the service address includes a folder path, keep it separate from the hostname and select the remote location when configuring the Mount or Sync. A successful connection test does not establish access to every path or permission to perform every operation.
Network and Certificate Verification
Allow the source addresses for the selected connection route on the remote service's port. With dedicated addresses, the route can use the site's defaults or an eligible Custom Domain. WebDAV carries requests and contents through its HTTP connection; it does not need FTP's separate passive data-port range.
Agent routing reaches a private service from the Agent's network. The Agent must be able to resolve and reach that endpoint.
For HTTPS, Files.com verifies the remote certificate's hostname, validity, and trust chain by default. Allowing a non-matching or untrusted certificate bypasses identity checks. Ask the operator to correct an unexpected certificate failure; encryption alone does not establish that the connection reached the intended service.
Upload Delivery and Capacity
With Buffered Uploads set to Automatic, Files.com stages WebDAV uploads before forwarding them to the service. A completed client upload then confirms receipt by Files.com, rather than availability on the remote server. Buffered Uploads explains onward delivery and required file processing.
WebDAV uses parallel HTTP requests and has no configurable Max connections setting in Files.com. The remote service can still impose request or capacity limits. Account for the combined workload when recurring transfers slow down or fail, and use the WebDAV troubleshooting reference to distinguish connectivity, credentials, certificates, and operation permissions.