> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/webdav.md).

# WebDAV

Configure WebDAV entry settings in Remote Desktop Manager, including host, credentials, directories, proxy, WebDAV over SSH, and logging options.

This article details the many settings and options available for ***WebDAV*** session entries in Remote Desktop Manager.

<table data-header-hidden><thead><tr><th width="200"></th><th></th></tr></thead><tbody><tr><td><strong>SETTINGS</strong></td><td><strong>DESCRIPTION</strong></td></tr><tr><td><strong>Name</strong></td><td>The name of the entry.</td></tr><tr><td><strong>Folder</strong></td><td>The folder where the entry is located. Click the browse button to select a folder, or click the add (<em><strong>+</strong></em>) button to create a new one.</td></tr><tr><td><strong>Display</strong></td><td><p>How the entry opens:</p><ul><li><strong>Embedded (tabbed)</strong> — Opens the entry in a tab of the main window.</li><li><strong>Undocked</strong> — Opens the entry in a separate window. Additional lists let you choose the monitor and the virtual desktop where the window opens.</li></ul><p>On Linux, the list also offers <em><strong>Default (inherited)</strong></em>, which uses the display mode of the nearest parent folder that sets one, otherwise the default of the entry type. The mode it resolves to is shown next to the list.</p></td></tr><tr><td><strong>Host</strong></td><td>Where the host of the entry comes from. <em><strong>Host configured</strong></em> uses the <em><strong>Host</strong></em> entered in the <em><strong>General</strong></em> tab. <em><strong>Linked</strong></em> uses a host entry from the vault selected in the <em><strong>Vault</strong></em> list. <em><strong>Inherited</strong></em> uses the host of a parent folder.</td></tr><tr><td><strong>Credentials</strong></td><td>How the credentials of the entry are provided. Select a credential mode from the list. When the credentials do not come from the entry itself, the <em><strong>Username</strong></em>, <em><strong>Password</strong></em>, and <em><strong>Always ask for password</strong></em> settings of the <em><strong>General</strong></em> tab are disabled.</td></tr></tbody></table>

### General

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Host</strong></td><td>The host name or IP address of the WebDAV server. This field is required when the <em><strong>Host</strong></em> of the entry is <em><strong>Host configured</strong></em>.</td></tr><tr><td><strong>Port</strong></td><td>The port of the WebDAV server. The default port is 80, or 443 when <em><strong>Use SSL</strong></em> is selected.</td></tr><tr><td><strong>Username</strong></td><td>The username used to sign in to the WebDAV server. This field is required when the credentials come from the entry itself.</td></tr><tr><td><strong>Use SSL</strong></td><td>Connects to the WebDAV server over SSL.</td></tr><tr><td><strong>Password</strong></td><td>The password used to sign in to the WebDAV server. This field is required when it is enabled. It is disabled when <em><strong>Always ask for password</strong></em> is selected. It is unavailable when the <em><strong>Disable password saving in vaults</strong></em> system setting is enabled.</td></tr><tr><td><strong>Always ask for password</strong></td><td>Asks for the password each time the entry is opened instead of saving it in the entry.</td></tr><tr><td><strong>Home directory</strong></td><td>The home directory on the WebDAV server. This field is required.</td></tr><tr><td><strong>Starting location</strong></td><td>The remote directory displayed when the session opens.</td></tr><tr><td><strong>Show files in tree view</strong></td><td>Displays files, as well as folders, in the tree view of the session.</td></tr></tbody></table>

### Proxy

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Use proxy</strong></td><td>Connects to the WebDAV server through a proxy. The other proxy settings are shown when this option is selected.</td></tr><tr><td><strong>Proxy URL</strong></td><td>The address of the proxy server.</td></tr><tr><td><strong>Port</strong></td><td>The port of the proxy server.</td></tr><tr><td><strong>Proxy type</strong></td><td><p>The type of proxy:</p><ul><li><strong>HTTP</strong></li><li><strong>HTTPS</strong></li><li><strong>Socks4</strong></li><li><strong>Socks4a</strong></li><li><strong>Socks5</strong></li></ul></td></tr><tr><td><strong>Bypass proxy on local</strong></td><td>Connects directly, without the proxy, to local addresses.</td></tr><tr><td><strong>Username</strong></td><td>The username used to sign in to the proxy. Leave it empty when the proxy does not require authentication.</td></tr><tr><td><strong>Domain</strong></td><td>The domain of the proxy username.</td></tr><tr><td><strong>Password</strong></td><td>The password used to sign in to the proxy. Leave it empty when the proxy does not require authentication.</td></tr></tbody></table>

### SSH settings

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Use WebDAV over SSH</strong></td><td>Connects to the WebDAV server through an SSH connection. The other SSH settings are enabled when this option is selected.</td></tr><tr><td><strong>Host</strong></td><td>The host name or IP address of the SSH server.</td></tr><tr><td><strong>Port</strong></td><td>The port of the SSH server.</td></tr></tbody></table>

**Credential**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Username</strong></td><td>The username used to sign in to the SSH server.</td></tr><tr><td><strong>Password</strong></td><td>The password used to sign in to the SSH server. It is disabled when <em><strong>Always ask for password</strong></em> is selected.</td></tr><tr><td><strong>Always ask for password</strong></td><td>Asks for the SSH password each time the entry is opened.</td></tr></tbody></table>

**Private key**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Private key</strong></td><td>The source of the private key used to authenticate to the SSH server, such as <em><strong>No private key</strong></em>, <em><strong>File (local)</strong></em>, <em><strong>Embedded data</strong></em>, <em><strong>My personal SSH key</strong></em>, or <em><strong>Linked</strong></em>. The options offered depend on the data source. The fields below the list change with the selected source.</td></tr><tr><td><strong>Vault</strong></td><td>The vault that holds the linked private key entry. This field is shown when the private key comes from a linked entry.</td></tr><tr><td><strong>Entry</strong></td><td>The entry that holds the private key. This field is shown when the private key comes from a linked entry.</td></tr><tr><td><strong>File</strong></td><td>The private key file. This field is shown with <em><strong>File (local)</strong></em>.</td></tr><tr><td><strong>Private key data</strong></td><td>The content of the private key. This field is shown with <em><strong>Embedded data</strong></em>. Buttons let you generate, view, paste, browse for, or clear the key.</td></tr><tr><td><strong>Passphrase</strong></td><td>The passphrase of the private key. This field is shown with <em><strong>File (local)</strong></em> and <em><strong>Embedded data</strong></em>.</td></tr><tr><td><strong>Always prompt for passphrase</strong></td><td>Asks for the passphrase each time the entry is opened. This option is shown with <em><strong>File (local)</strong></em> and <em><strong>Embedded data</strong></em>.</td></tr></tbody></table>

**Advanced**

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Algorithm support</strong></td><td>Choose between <em><strong>Default</strong></em> and <em><strong>Custom</strong></em>. With <em><strong>Custom</strong></em>, click the button next to the list to choose the SSH algorithms to support.</td></tr><tr><td><strong>Use SSH authentication agent</strong></td><td>Authenticates to the SSH server with an SSH authentication agent. When this option is selected, the private key of the entry is ignored to avoid conflicts with the agent.</td></tr></tbody></table>

### Advanced

<table><thead><tr><th width="220">SETTINGS</th><th>DESCRIPTION</th></tr></thead><tbody><tr><td><strong>Show local files</strong></td><td>Displays the local files next to the remote files in the session.</td></tr><tr><td><strong>Local path</strong></td><td>The local folder displayed when <em><strong>Show local files</strong></em> is selected.</td></tr><tr><td><strong>Show logs</strong></td><td>Displays the logs in the session. This option is cleared when the entry is saved with <em><strong>Verbose</strong></em> set to 0.</td></tr><tr><td><strong>Verbose</strong></td><td>The level of detail of the logs, from 0 to 4. The level is saved as 0 when <em><strong>Show logs</strong></em> is cleared.</td></tr><tr><td><strong>Log to file</strong></td><td>Writes the logs to a file.</td></tr><tr><td><strong>File path</strong></td><td>The path and name of the log file. This field is available when <em><strong>Log to file</strong></em> is selected.</td></tr></tbody></table>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.devolutions.net/rdm/knowledge-base/knowledge-base-articles/entry-settings/webdav.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
