WebDAV Connections

The Files.com Agent can act as a secure WebDAV proxy that routes WebDAV Remote Server connections from your Files.com site to an internal, on-premise WebDAV server. Files.com reaches WebDAV servers that live entirely inside private networks, without requiring those servers to be exposed to the public internet.

Prerequisites

To use Agent-routed WebDAV connections, you must run a Files.com Agent on a system that can reach the internal WebDAV server over the network.

The Agent host must have outbound access to the WebDAV server on its configured port, typically TCP 443 for HTTPS or TCP 80 for HTTP.

The Agent configuration must explicitly allow WebDAV routing, and the internal WebDAV server must accept connections from the Agent host.

Enable WebDAV Routing on the Agent

Files.com enables WebDAV routing through the Agent configuration file. Edit the configuration file and set the integrations value to include "webdav".

Save the change and restart the Agent so it can advertise WebDAV routing support to your Files.com site.

Configuration example:

integrations = ["webdav"]

Once the Agent restarts, it becomes available for WebDAV routing.

Configure a WebDAV Remote Server to Use the Agent

After the Agent has been configured for WebDAV routing, configure the WebDAV Remote Server in Files.com.

When creating or editing the Remote Server, enter the internal hostname or IP address of the WebDAV server. Enable Agent routing and select the Agent that runs inside the same private network as the WebDAV server.

From that point forward, Files.com routes all WebDAV traffic for this Remote Server through the selected Agent.

Transfer Performance Boost

Agent-routed connections improve transfer speed compared to direct legacy-protocol access. WebDAV is a chatty, latency-sensitive protocol that performs poorly over long-distance or high-latency networks. The Files.com Agent communicates with Files.com using a transfer mechanism built for high throughput and resilience.

Files.com transfers data to the Agent at speeds far exceeding what WebDAV can sustain over the public internet. The Agent then performs the WebDAV transfer locally within your private network, where latency is low and bandwidth is high. This separation removes WebDAV's performance bottleneck from the long-haul portion of the transfer.