WebDAV Troubleshooting
Platform Notice: Data Center - This article applies to Atlassian products on the Data Center platform.
Note that this knowledge base article was created for the Data Center version of the product. Data Center knowledge base articles for non-Data Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
This page provides some troubleshooting tips on configuring a WebDAV client to work with Confluence pages and on general WebDAV functionality.
Adding WebDav Logging
There are two places to configure extra logging:
1. Confluence Logging
In Confluence, add the following line in the Logging and Profiling console and set the logging level to
DEBUG.:com.atlassian.confluence.extra.webdav
- Access Confluence using a Webdav client again, and replicate the authentication problem.
Check the
atlassian-confluence.logfile in the confluence-home directory. Logging similar to the following will appear:2010-03-16 11:57:50,274 DEBUG [http-8000-10] [extra.webdav.servlet.ConfluenceWebdavServlet] service Microsoft-WebDAV-MiniRedir/6.1.7600, OPTIONS /plugins/servlet/confluence/default
In this example, the
Microsoft-WebDAV-MiniRedirWebDav clientversion 6.1.7600is displayed.
2. Tomcat Logging
You can use Tomcat's Valve Component to give you WebDAV accesses attempt.
Related Topics
Audit Confluence Using the Tomcat Valve Component
Unable to authenticate while mapping a WebDAV client network drive in Confluence
Existing Knowledge Base Articles
Open Bugs and Feature Requests
| type | key | summary | assignee | reporter | priority | status | resolution | created | updated | due |
|---|---|---|---|---|---|---|---|---|---|---|
|
Data cannot be retrieved due to an unexpected error. View these issues in Jira |
||||||||||