Describe the bug
Uploading large files (say ~2-3GB) from a phone to seafdav is oftentimes problematic. Sometimes files end up corrupted, and deletions fail to sync altogether.
To Reproduce
create ~2GB file in local device
try to upload said file to seafdav
notice 499 http codes in nginx logs
retry the process
client detects conflicts
(sometimes the original upload fails with uploaded file being smaller than expected, but that behavior is inconsistent)
delete already synced file on local device
sync the deletion with webdav remote
notice deletion is not propagated to remote
Expected behavior
Files creation & deletions synced properly, no 499 HTTP codes in nginx logs.
Relevant portion from nginx' seafdav.access.log from a sync session:
Manual sync was triggered at 15:20:00.
Note the signal-2024-09... files are the large ones that cause problems.
Describe the bug Uploading large files (say ~2-3GB) from a phone to seafdav is oftentimes problematic. Sometimes files end up corrupted, and deletions fail to sync altogether.
To Reproduce
Expected behavior Files creation & deletions synced properly, no 499 HTTP codes in nginx logs.
Relevant portion from nginx' seafdav.access.log from a sync session:
Manual sync was triggered at 15:20:00. Note the
signal-2024-09...files are the large ones that cause problems.seafdav.log:
Environment:
Where exactly to run
wsgidavcommand? Running it from docker container doesn't find it on our PATH.Which WSGI server was used (cheroot, ext-wsgiutils, gevent, gunicorn, paste, uvicorn, wsgiref, ...)?
Unsure, but seafile is running on
jammy-1.0.2image, relevant dependencies installed by this statementWebDAV client: FolderSync Pro 4.0.1 running on Android 14.
Additional context