Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing listening host for webdav #478

Closed
jthomaschewski opened this issue Dec 27, 2013 · 2 comments
Closed

Changing listening host for webdav #478

jthomaschewski opened this issue Dec 27, 2013 · 2 comments

Comments

@jthomaschewski
Copy link

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?

@florentx
Copy link

too bad, I have exactly this issue (nginx and seafile on different hosts).

@JensErat
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants