Fix Seafdav: WebDAV MOVE command causing 502

[jacquesblp]

When using Seafdav, probably when updating an existing file, the WebDAV client will perform a PUT to a temporary file, then a MOVE to replace the destination file. The MOVE operation fails after passing through a reverse proxy with SSL termination.

==> /var/log/nginx/seafdav.access.log <==
192.168.100.137 10.42.2.33 [22/Oct/2025:13:47:04 +0700] "PUT /seafdav/mylib/file.txt.tmp.18881965 HTTP/1.1" 401 139 "-" "okhttp/4.12.0" 0.001
192.168.100.137 10.42.1.98 [22/Oct/2025:13:47:07 +0700] "PUT /seafdav/mylib/file.txt.tmp.18881965 HTTP/1.1" 201 372 "-" "okhttp/4.12.0" 1.993
192.168.100.137 10.42.3.74 [22/Oct/2025:13:47:07 +0700] "MOVE /seafdav/mylib/file.txt.tmp.18881965 HTTP/1.1" 401 139 "-" "okhttp/4.12.0" 0.001
192.168.100.137 10.42.4.98 [22/Oct/2025:13:47:07 +0700] "MOVE /seafdav/mylib/file.txt.tmp.18881965 HTTP/1.1" 502 588 "-" "okhttp/4.12.0" 0.044

Solution: remove https from the Destination header.

See https://forum.seafile.com/t/seafdav-move-command-causing-502/11582/25

[imwhatiam]

Hello, this issue has been explained in our document. Could you try to solve this problem according to the method in the document?

https://manual.seafile.com/latest/extension/webdav/?h=seafdav#cant-renamemove-filefolder