WebDav - wrong redirect

Seafile Client
1

Hi.
I have problem with my WebDav on SeaFile 10.0.1.
I configured it as in the manual.
seafdav.conf:

[WEBDAV]
enabled = true
port = 8080
workers = 5
fastcgi = false
share_name = /seafdav
timeout = 1200

Nginx conf:

location /seafdav {
proxy_pass http://172.30.28.2:8080/seafdav;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Host $server_name;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_read_timeout 1200s;
client_max_body_size 0;

proxy_set_header Destination "http:$nossl_destination";

access_log      /var/log/nginx/seafdav.access.log seafileformat;
error_log       /var/log/nginx/seafdav.error.log;
}

After entering cloud.temp.com/seafdav
Everything seems normal but when I try to go to the scan folder the path changes to cloud.temp.com/scan and I get the message “Unfortunately, the page you requested could not be found”. The path is obviously wrong, missing /seafdav.

In my previous installation with SeaFile Server ver. 9 with the same configuration everything worked fine.

Please help me solve this problem.

Regards
Dawid

1 Like
2

I found solution for this. After replacing WsgiDAV in SeaFile Server 10 files to version WsgiDAV/3.0.4 from Seafile Server 9 everything works great.

3

You don’t need /seafdav in the proxy_pass, just leave it like this:

proxy_pass http://172.30.28.2:8080;

And add this

proxy_set_header Destination "http:$nossl_destination";
4

Can you clarify what

proxy_set_header Destination "http:$nossl_destination";

is doing?

-Thanks

5

Fixes this Seafdav - MOVE command causing 502 - #23 by eruditewriter

Not sure if it’s still needed with version 10 where there have been another upgrade of wsgidav version.