Allow custom HTTP headers in Seafile client and syncing client

Hi there, I’m a new user of Seafile. Thank you very much for building the great software! I’m filling this feature request for a scenario where the seafile server is behind a reverse proxy (like pangolin, or Cloudflare tunnel) that needs another layer of authentication.

The issue is, when seafile server runs behind the reverse proxy and the proxy requires an extra authentication, mobile client and desktop client can’t handle this and won’t be able to log in. Currently the workaround is to expose the seafile directly to the internet without proxy authentication. However, most such reverse proxies accept authentication with special HTTP headers (like token headers). If the desktop/mobile client can allow such configuration during login (and sends the headers for all the subsequent requests to the domain), the software can stay behind the proxy while functional. This solves problem for mobile/desktop client specifically.

1 Like

How did you manage to get the clients to work with Pangolin bypass? I tried several different ways and just could not get the Sync client to connect. I checked Seafile docs and I must’ve missed it but I didn’t see it explicitly stated what the URL looks like from the client that then needs to be entered as bypass in Pangolin.

All that said, I also support this feature request! :slight_smile: