WebDav MOVE command fails

[gabriele-v]

Hello,
I've moved my binary Seafile 11 installation to Docker.

In my binary installation I've applied Nginx changes suggested here:
https://forum.seafile.com/t/seafdav-move-command-causing-502/11582/49

proxy_set_header   X-Forwarded-Proto $scheme;

Now in Docker I'm facing the same issue again.
SSL is not terminated on Nginx inside Seafile contatiner but on a Nginx Proxy Manager container that forwards in HTTP to Seafile container.

I've seen that in Seafile Nginx container the above line is present, I've removed it and everything works succesfully.
Considering that mar10/wsgidav#183 has been fixed and already added to Seafile 11 code, I don't think the above workaround is needed anymore.

Thanks!

[imwhatiam]

I've seen that in Seafile Nginx container the above line is present,

Hello.

Are you saying that in your place, there is this line in the nginx configuration file used by Seafile docker?

proxy_set_header   X-Forwarded-Proto $scheme;

I just checked the nginx configuration template we use to create the Seafile docker image, there is not the above statement.

[gabriele-v]

I'm quite sure that during migration I haven't changed Seafile container nginx configuration but only Seafile and Seahub configuration files. I'll try this evening to spin up a fresh container and see what happens.

EDIT: I think it has been removed here 735fe08 which only affects Seafile v12 images, while I've migrated a v11 installation

[imwhatiam]

EDIT: I think it has been removed here 735fe08 which only affects Seafile v12 images, while I've migrated a v11 installation

It should be like this. In the latest version, there is no relevant configuration anymore.