You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running nginx on a different host and want to deploy seafile webdav which is currently not possible because it's listening on 127.0.0.1 only and not configurable (hard configured in seafile-controller.c).
It would be great to have an option "host" in seafdav.conf to configure interface on which webdav http or fastcgi service is listening.
Currently (2.1.0/master) host is hard configured to "0.0.0.0" (all interfaces) for webdav http service and not set for fastcgi (defaults to 127.0.0.1).
Is there any reason why "--host 0.0.0.0" (seafile-controller.c line 372) is only set for non fastcgi seafdav only?
The text was updated successfully, but these errors were encountered:
Stumbled into the same issue. I would propose to add another seafdav option, host which allows you to configure the IP address to listen on. start_seafdav() seems to be the relevant code portion for this (and like a very easy fix), but I'm not sure what is additionally required for adding new options.
I'm running nginx on a different host and want to deploy seafile webdav which is currently not possible because it's listening on 127.0.0.1 only and not configurable (hard configured in seafile-controller.c).
It would be great to have an option "host" in seafdav.conf to configure interface on which webdav http or fastcgi service is listening.
Currently (2.1.0/master) host is hard configured to "0.0.0.0" (all interfaces) for webdav http service and not set for fastcgi (defaults to 127.0.0.1).
Is there any reason why "--host 0.0.0.0" (seafile-controller.c line 372) is only set for non fastcgi seafdav only?
The text was updated successfully, but these errors were encountered: