Bug 62638 - WebDAV gives system error 67 or 53 on Windows 10
Summary: WebDAV gives system error 67 or 53 on Windows 10
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_dav (show other bugs)
Version: 2.5-HEAD
Hardware: PC All
: P2 normal (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
Depends on:
Reported: 2018-08-20 08:14 UTC by alex1452
Modified: 2018-09-05 21:34 UTC (History)
0 users


Note You need to log in before you can comment on or make changes to this bug.
Description alex1452 2018-08-20 08:14:27 UTC
I am on:
Server version: Apache/2.4.29 (Ubuntu)
Server built:   2018-06-07T21:10:10

I have set WebDAV with apache 2.4 using the following lines:
Alias /mydav /srv/mydav
<Location /mydav>
	Dav On
	AuthType Basic
	AuthName "WebDAV"
	AuthUserFile /etc/apache2/.htpasswd

	<LimitExcept GET OPTIONS>
		Require valid-user

I have activated basic authentication without SSL:

However, Windows 10 gives the following error messages:
net use * http(s)://server.tld/mydav /user:user - System Error 67
net use * \\server.tld@SSL\mydav /user:user - System Error 53

Apache does not show anything in error log. Access log contains the following entry: - - [20/Aug/2018:08:12:50 +0000] "OPTIONS / HTTP/1.1" 200 218 "-" "Microsoft-WebDAV-MiniRedir/10.0.17134" - - [20/Aug/2018:08:12:50 +0000] "PROPFIND /mydav HTTP/1.1" 301 580 "-" "Microsoft-WebDAV-MiniRedir/10.0.17134" - - [20/Aug/2018:08:12:50 +0000] "PROPFIND /mydav/ HTTP/1.1" 403 520 "-" "Microsoft-WebDAV-MiniRedir/10.0.17134"

The issue seems to be a different way that the windows mini-redirector communicates with httpd. Other clients like Cadaver work with this setup. However, with the (still) high relevance of Windows, it seems to be importan t to correctly work with Windows 10 WebDav redirector.

Side note: I can connect with the same windows instance to other WebDav sites (eg. gmx.net) without any problems. So the issue does not seem to be the Windows setup.
Comment 1 William A. Rowe Jr. 2018-08-20 15:52:13 UTC
The responses were success, redirect, forbidden.

Somehow you've failed to permit dav directives in the desired url space.

This issue tracker is for chasing defects in the software, please seek help from the users@httpd.apache.org mailing list or similar user communities about authorization and authentication.
Comment 2 William A. Rowe Jr. 2018-08-20 15:58:11 UTC
FYI this might be a clue, MS Win 10 client specific?

From Wikipedia;

In WebDAV, the 403 Forbidden response will be returned by the server if the client issued a PROPFIND request but did not also issue the required Depth header or issued a Depth header of infinity

You might look at a Wireshark capture to find out how Windows 10 broke its query, if that is the case?
Comment 3 alex1452 2018-09-04 03:34:54 UTC
Thank you for your comment. It is indeed Windows 10 specific. The same setup works with Windows 7 and other WebDAV clients. My setup is vanilla apache without any modification except the mentioned lines in my original post. If the problem is that I "somehow ... failed to permit dav directives in the desired url space.", than tnis is an issue with the standard setup.

This is a vanilla install of Ubuntu 18.04 without ANY modification except the mentioned changes.
Comment 4 William A. Rowe Jr. 2018-09-05 21:34:34 UTC
Can you sniff the wire to determine what Depth arg was passed by Windows 10 (if any?) as indicated in my later comment?