WebDAV Connection
Description
This metadata type registers a named WebDAV endpoint in your project. Hop exposes each connection under the connection name as a VFS scheme, so you reference files with:
myConnectionName:///path/under/webdav/root
The WebDAV root URL in the metadata must be a full Apache Commons VFS WebDAV URL (webdav4:// for HTTP or webdav4s:// for HTTPS), including the path to your DAV root (for example a Nextcloud folder root such as /remote.php/dav/files/username/).
Credentials are configured in this metadata object and applied through VFS—they are not embedded in Hop file paths.
For the underlying webdav4 / webdav4s URI syntax and options, see VFS (WebDAV section).
Many hosted servers redirect HTTP to HTTPS with 301. Use webdav4s:// in WebDAV root URL when the server expects TLS, otherwise listing or type detection can fail while desktop clients (that follow redirects for WebDAV methods) may still work. |
| Username, password, and WebDAV root URL support variable substitution. Passwords can be stored encrypted in metadata; Hop decrypts them when resolving the connection. |
Options
| Option | Description |
|---|---|
Name | Name of this connection; used as the URI scheme in paths ( |
Description | Optional longer description |
WebDAV root URL | Full URL including scheme |
Username | User name for authentication (optional if the server allows anonymous access) |
Password | Password or application password; supports variables and encrypted values |
Follow HTTP redirects | Passed to the HTTP client (see VFS/WebDAV provider behavior for redirect limits on WebDAV methods) |
Preemptive basic authentication | Sends credentials proactively for servers that require it |
Tips
-
To verify a connection, open File → Open (or any file dialog) and browse
YourConnectionName:///or drill into a subfolder path. -
Prefer
webdav4s://for Nextcloud and similar hosts that enforce HTTPS. -
Pick a Name that does not clash with built-in VFS schemes (
file,ftp,http, …) or other registered plugins (s3,azure,gs, etc.).