Add custom HTTP headers in media providers

Feature requests
1

Feature description:

Add fields to custom HTTP headers when connecting to media providers (other header that basic authentication).

Problem solved:

I used Navidrome as server behind Cloudflare tunnels and it could be interesting to custom HTTP headers in media providers.

As now, we can use a proxy username and password to set a Authorization: Basic*** HTTP header but we cannot add custom headers.

For your information, I can reach my Navidrome server with curl with the following curl command :

curl -i "https://my.navidrome.server" -H "CF-Access-Client-Id: xxxx" -H "CF-Access-Client-Secret: xxxx"

Brought benefits:

Improve security for self hosted servers.

Other application solutions:

 

 

Additional description and context:

 

 

Screenshots / Mockup:

    

2

Hello, and thank you for this great application !

3

@Tolriq Thank you ! I’ll try it.

4

@Makozique With this implemented, could you explain how you got it working please?
I have Jellyfin accessible behind a CF tunnel, with Google & Pin auth, and can access it via web browser.
I tried creating a CF Service Token, and putting those two into Symfonium media provider headers, but Symfonium still fails to connect when outside of home LAN.
I have ensured the CF Zero Trust Application | Policy | has a Service Auth action with include.