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

1. In Confluence, add the following line in the Logging and Profiling console and set the logging level to DEBUG.: 

   com.atlassian.confluence.extra.webdav

2. Access Confluence using a Webdav client again, and replicate the authentication problem.

3. Check the atlassian-confluence.log file 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-MiniRedir WebDav client version 6.1.7600 is 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

• Page:
  Accessing a Space via Webdav Returns a Blank Page
• Page:
  WebDAV Client Timed Out when Accessing Confluence Space or Directory
• Page:
  Some pages do not exist when accessing Confluence via WebDAV
• Page:
  List Pages Tree View Loads Forever
• Page:
  Unable to Setup Microsoft Network Drive to Connect to Webdav
• Page:
  'Error! Filename not specified' when Saving a Document from Office Connector
• Page:
  Unable to access WebDAV when Confluence is Behind Apache or Nginx Proxy
• Page:
  After Upgrade, Editing Via WebDAV Fails
• Page:
  Some Attachments Cannot Be Edited - Clicking on the Edit Function Does Not Work
• Page:
  In Microsoft Windows, the WebDAV Drive Share Is Not Found
• Page:
  Unable to authenticate while mapping a WebDAV client network drive in Confluence

Open Bugs and Feature Requests