-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker Seafile 11 Seafdav (Webdav) upload issue: 0 Byte Files #2809
Comments
Hello, Seafile’s seafdav is based on the wsgidav project(GitHub - mar10/wsgidav: A generic and extendable WebDAV server based on WSGI 1). Seafile version 10 uses wsgidav 4.1, while version 11 uses wsgidav 4.3. It seems that wsgidav added some checks in version 4.3, which caused your issue. We have also conducted tests, and it seems that this issue only occurs when connecting to seafdav using Windows File Explorer. Other WebDAV clients do not encounter this problem. We will debug it to see if they can resolve this problem. |
Hi @imwhatiam so that means that with wsgidav as standalone the bug would also be there? So the functionality without any apps is the most important thing for using Seafile with Windows. Thanks and please keep me updated |
@nobe80 We will try to solve this problem, but we need to gain a deep understanding of the WsgiDAV project, which may take quite a long time. |
@imwhatiam Thanks for that info. Do you know how long Seafile 10 will work further? regards |
@imwhatiam Any news regarding this issue? |
Hi @imwhatiam , do you have any news on this? The issue is still pending since summer this year! We need that feature because the native webdav is the most important function and the reason why we are using Seafile! thanky & regards |
Are you sure about this? I see the same misbehaviour using
This bug is really a bummer. My strategy to re-install my vserver farm after a catastropic failure in the VMs is based on the possibility to mount via WebDAV. And I learned the hard way that this fails now as I upgraded my Seafile server. Cheers! |
Hi,
i have faced an issue with Seafile webdav (Seafdav) when i use Seafile Version 11 after upgrade to 11.0.11.
The issue is the follow:
In Windows file explorer i have successful a Webdav drive over https to the Seafile server. So seafdav is enabled, we can see all folders. When i upload some files like pdf or simple text files i get an error “…
file is to big…” and i have 0 Bytes files in the folder.
When i downgrade to Seafile Version 10 again no problems at all. Everything works fine then.
We use Seafile docker community.
Does anyone have a hint what could be the reason?
The text was updated successfully, but these errors were encountered: