-
-
Notifications
You must be signed in to change notification settings - Fork 160
Closed
Labels
client-miniredirRelated to Microsoft Window Mini-RedirectorRelated to Microsoft Window Mini-Redirectorclient-relatedThis problem is probably caused by incompatible WebDAV client behavior?This problem is probably caused by incompatible WebDAV client behavior?core
Description
I never really had problems using Wsidav on a linux environment.
The thing is: I'm now using Windows and since official Windows Webdav doesn't work, I stick to wsgidav. I can open files without problems from a wsgidav mount point, but I can't copy files to a wsgidav folder. I just can't. Sometimes it says "No space left" which is not true since I got 80gb free on both source and destination folders.
I have this problem on Windows since version 2.x.x. I thought it would change when I've updated, but the same thing happens.
I'm using it with auth=anonymous since I don't know how to use authentication on Windows.
Metadata
Metadata
Assignees
Labels
client-miniredirRelated to Microsoft Window Mini-RedirectorRelated to Microsoft Window Mini-Redirectorclient-relatedThis problem is probably caused by incompatible WebDAV client behavior?This problem is probably caused by incompatible WebDAV client behavior?core
Projects
Milestone
Relationships
Development
Select code repository
Activity
gabriellluz commentedon Mar 25, 2019
Same problem using Android accessing a wsgidav folder.
mar10 commentedon Apr 22, 2019
I assume you mean that you have problems when the WebDAV client is Windows based, such as the Mini-Redirector that is used by the
> net use ...
command?Or does it make a difference on what OS the WsgiDAV server runs?
The mini.redirectors are known to have problems, sometimes they can be fixed by implementing a kind of quirks mode in the server behavior.
Could you give some more details, please:
gabriellluz commentedon Apr 22, 2019
I had the same problem using an Android client (Smart File Manager and Astro File Manager) and using both Windows 7 and Windows 10.
mar10 commentedon Apr 27, 2019
Some testing:
(1): Windows clients
No matter if SSL is enabled or not.
No matter if authentication is used or not.
No matter if on Windows the 'Automatically detect settings' option is disabled or not.
No matter if virus checker is enabled.
This is a single copy sequence for 6MB file:
Other problems on Windows include:
(2): macOS clients
Finder seems to work Ok.
gabriellluz commentedon Apr 29, 2019
Exactly. I don't have trouble using connecting to wsgidav on Ubuntu with rclone or whatever.
SteffenDE commentedon May 12, 2019
Okay, I'm sorry. I didn't read the whole issue very carefully. I do not experience this issue as I'm not using the default Filesystem provider and cheroot but rather a custom implementation + Gevent. Using the default configuration, the Windows clients are SLOW.
Using Gevent fixes these issues for me:
So: seems to be an issue with cheroot.
SteffenDE commentedon May 13, 2019
@gabriellluz It‘d be great if you could check if using
--server=gevent
fixes your performance issues.mar10 commentedon May 15, 2019
Some more information when running WsgiDAV on Windows 10 and accessing it with File Explorer from the same machine:
Run

wsgidav --host 0.0.0.0 --server ANY
, connect tohttp://localhost:8080/
:File Explorer is extremely slow (1-3 seconds delay between every file operation) when connecting to 'localhost'
No matter if: cheroot/gevent, SSL on/off, authenticated/anonymous
I assume this is a problem with my personal local network or DNS configuration.
E.g. using gevent:
Run

wsgidav --server gevent --host 0.0.0.0
, connect tohttp://192.168.0.17:8080/
Accessing using the IP address works fast with gevent:
Run

wsgidav --server cheroot --host 0.0.0.0
, connect tohttp://192.168.0.17:8080/
Accessing using the IP address still slow with cheroot:
Run

wsgidav --server cheroot --host 0.0.0.0
, connect tohttp://192.168.0.17:8080/
Increasing thread count to 100 for cheroot improves it:
Run

wsgidav --server cheroot --host 0.0.0.0
, connect tohttp://192.168.0.17:8080/
Increasing cheroot's thread count to 256 improves it even more:
Run

wsgidav --server cheroot --host 0.0.0.0
, connect tohttp://192.168.0.17:8080/
Increasing cheroot's thread count to 256 comes to a limit when we upload 300 images (instead of 50):
Run

wsgidav --server gevent --host 0.0.0.0
, connect tohttp://192.168.0.17:8080/
gevent also has a bump, but handles 300 images better:
7 remaining items