Allow custom HTTP Headers in Indexer / Downloader config #6245

New issue

Open

opened 2026-02-19 23:03:04 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-19 23:03:04 -05:00

Owner

Originally created by @ThomasDalla on GitHub (Dec 22, 2021).

Is there an existing issue for this?

I have searched the existing issues

Indexers / Downloaders can be behind services that require custom headers to be passed.
However, Radarr does not support passing custom headers in the indexers/downloaders configurations.

Describe the solution you'd like

In "Advanced Mode", allow specifying a set of key-pair values of custom http headers that are sent in the requests to the indexer/downloader.

Example:

{
  "CF-Access-Client-Id" : "my-client-id",
  "CF-Access-Client-Secret": "my-client-secret"
}

Describe alternatives you've considered

Passing it as a semi-column separated list:

CF-Access-Client-Id: my-client-id; CF-Access-Client-Secret: my-client-secret

Anything else?

For clarity, I am talking about this screen:

AB#2247

Originally created by @ThomasDalla on GitHub (Dec 22, 2021). ### Is there an existing issue for this? - [X] I have searched the existing issues ### Is your feature request related to a problem? Please describe Indexers / Downloaders can be behind services that require custom headers to be passed. However, Radarr does not support passing custom headers in the indexers/downloaders configurations. ### Describe the solution you'd like In "Advanced Mode", allow specifying a set of key-pair values of custom http headers that are sent in the requests to the indexer/downloader. Example: ``` { "CF-Access-Client-Id" : "my-client-id", "CF-Access-Client-Secret": "my-client-secret" } ``` ### Describe alternatives you've considered Passing it as a semi-column separated list: ``` CF-Access-Client-Id: my-client-id; CF-Access-Client-Secret: my-client-secret ``` ### Anything else? For clarity, I am talking about this screen: ![image](https://user-images.githubusercontent.com/609945/147145567-ac898058-a2d0-441e-9d61-fd5b6674e4b2.png) [AB#2247](https://dev.azure.com/Servarr/7ab38f4e-5a57-4d70-84f4-94dd9bc5d6df/_workitems/edit/2247)

deekerman added the

Type: Feature Request

Area: Download Clients

Status: Unlikely

Status: Needs Triage

labels

2026-02-19 23:03:04 -05:00

deekerman commented

2026-02-19 23:03:05 -05:00

Author

Owner

@ta264 commented on GitHub (Dec 22, 2021):

While this might be nice to add I wouldn't hold your breath!

@ta264 commented on GitHub (Dec 22, 2021): While this might be nice to add I wouldn't hold your breath!

deekerman commented

2026-02-19 23:03:05 -05:00

Author

Owner

@krazy-glue commented on GitHub (Feb 3, 2025):

this would be really useful, and not only one person would be using this.
I'm using my SERVARRs on a distant machine from my downloader and the prowlarr instance, I'm trying to protect every instances behind the cloudflare access.

the android app NZB360 allow us to add a header to each service we can configure exactly for this.

@krazy-glue commented on GitHub (Feb 3, 2025): this would be really useful, and not only one person would be using this. I'm using my SERVARRs on a distant machine from my downloader and the prowlarr instance, I'm trying to protect every instances behind the cloudflare access. the android app NZB360 allow us to add a header to each service we can configure exactly for this.