search

haiwen / seafile

High performance file syncing and sharing, with also Markdown WYSIWYG editing, Wiki, file label and other knowledge management features.
http://seafile.com/
Other
12.25k stars 1.54k forks source link

[Feature request] Make the client (2.0) connect via HTTP/HTTPS only #393

Closed moonwhaler closed 8 years ago

moonwhaler commented 11 years ago

After finally succeeding in setting up the server behind a Nginx HTTPS proxy, installing a (Windows) client was the next step.

I realized however that the client will connect via HTTP/HTTPS and even lists the libraries, but won't upload/download anything if the ccnet port (default) 10001 and seaf-server port (default) 12001 are not open!

Please make (all) the clients work with HTTP/HTTPS only. Currently ownCloud, Dropbox and Google Drive support this. I would love to have it in Seafile, as well!

killing commented 11 years ago

It will be implemented in the future. It requires a lot changes to the current code.

moonwhaler commented 11 years ago

It is a huge enhancement for me, because my company blocks all ports except HTTP & HTTPS. Since I think this is normal in "bigger companies" or companies with good firewall administrators, I'm currently only able to access my Seafile server through a web browser, which is okay for now. For sync I'm going with Google Drive / Dropbox for the time being... Thank you!

fenderle commented 10 years ago

What about building a proxy into seafile-client / seafile which uses an upgraded HTTP connection to tunnel the two additional ports to the server?

moonwhaler commented 10 years ago

I still think this is a big feature addition for Seafile. Maybe you should put it somewhere on the roadmap. :+1: I understand that the mobile client connects through port 8000 (httpserver), maybe this can be achieved for the desktop client, as well...?

shoeper commented 8 years ago

has been implemented.