Support custom HTTP headers for Navidrome connections
Maintainers usually reply within 6 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
Research direction
Start by locating the Navidrome configuration and the code paths that make Subsonic API requests and stream audio. Check how configuration is parsed and how request headers are set in both paths; the issue does not name specific files or tests. Done means optional configured headers are sent with both API and streaming requests, while existing configurations continue to work.
Written by the indexing model from the issue text.
Description
Problem
Navidrome servers protected by Cloudflare Access cannot currently be used with cliamp because Cloudflare service tokens require custom headers on API and streaming requests.
Proposal
Allow optional custom HTTP headers in the Navidrome configuration, for example:
[navidrome.headers]
CF-Access-Client-Id = "$CF_ACCESS_CLIENT_ID"
CF-Access-Client-Secret = "$CF_ACCESS_CLIENT_SECRET"
The headers would need to apply to both Subsonic API calls and audio streams. Generic headers could also support other authenticating reverse proxies.
Mockups / references
Amperfy recently added similar support: https://github.com/BLeeEZ/amperfy/commit/9de99512639308634f6b40c1f7187b6391674333
- Dominant language
- Go
- Stars
- 4.4k
- Forks
- 307
- Avg merge
- 4d 18h
- Merged PRs (30d)
- 13
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from bjarneo/cliamp
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 6 days
-
Show the Podcast episodes in newest first orderPossibly taken @lchojnack claimed this 14 days ago. Openenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
bjarneo/cliamp#520 · 2 reactions ·
Maintainers usually reply within 6 days
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 6 days
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
limitlessprojects/Go-Hybrid#3342 ·
Maintainers usually reply within 1 day
-
status/ready type/bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
buildpacks/pack#2733 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
kind/bug needs-priority needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
konveyor/tackle2-hub#1166 · 1 comment ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
router-for-me/CLIProxyAPI#7209 ·
Maintainers usually reply within 1 day