As fixed in #11, the Windows 10 client has problems with 301 redirects issued by the Apache server. This is what happens:
Windows requests PROPFIND /Foldername without the trailing slash after /Foldername
Apache returns a 301 response to /Foldername/, which causes various errors in Windows, like not being able to create folders. In short: Windows can't deal with 301 redirects in WebDAV properly.
By adding an entry to the BrowserMatch list for ^Microsoft-WebDAV-MiniRedir (the Windows 10 WebDAV client), the problem is resolved with redirect-carefully. Please consider merging PR #11 to resolve this issue for Windows 10 users.
As fixed in #11, the Windows 10 client has problems with 301 redirects issued by the Apache server. This is what happens:
PROPFIND /Foldernamewithout the trailing slash after/Foldername301response to/Foldername/, which causes various errors in Windows, like not being able to create folders. In short: Windows can't deal with 301 redirects in WebDAV properly.By adding an entry to the BrowserMatch list for
^Microsoft-WebDAV-MiniRedir(the Windows 10 WebDAV client), the problem is resolved withredirect-carefully. Please consider merging PR #11 to resolve this issue for Windows 10 users.