Support for custom HTTP headers #649
peterjdolan
started this conversation in
Ideas
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
First of all thanks for such a great app! I really appreciate all the work you've put into it.
If I could configure Amperfy to set at least two custom HTTP headers on all of its requests to my Subsonic (Navidrome) server, then I would have access outside of my home network.
I host a Navidrome server and connect to it either via my internal home network or via Cloudflare Tunnels (https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/). This provides a lot of protection to my home systems, as the frontend is secured by the Cloudflare team and login is by Google accounts. They certainly do a better job of securing their endpoints than I can, and I don't trust any of my selfhosted apps enough to expose them publicly.
With this setup, Amperfy can't connect to my Navidrome instance's public URL, as Amperfy doesn't (and shouldn't) handle the Cloudflare login pages.
As an alternative, Cloudflare supports application service credentials (https://developers.cloudflare.com/cloudflare-one/access-controls/service-credentials/service-tokens/). If Amperfy could set two HTTP headers - CF-Access-Client-Id and CF-Access-Client-Secret - then it could bypass Cloudflare's login page and connect to my service.
There's one iOS subsonic app I'm aware of that supports custom HTTP headers - Nautiline - but I much prefer Amperfy.
Beta Was this translation helpful? Give feedback.
All reactions