feat(datasource/custom): allow sending custom headers #25677
Replies: 3 comments 5 replies
-
|
It's possible we might want to make this a generic |
Beta Was this translation helpful? Give feedback.
-
|
That would be even more useful, as right now host rules are very limited in the types of extra data that can be sent. If host rules were used, it would be good to be able to populate the value from env vars as well. |
Beta Was this translation helpful? Give feedback.
-
|
Both is possible, but host rules would be more useful IMO as we could support more complex routing setups. |
Beta Was this translation helpful? Give feedback.
-
|
@weikinhuang all config can be populated via env one way or another |
Beta Was this translation helpful? Give feedback.
-
|
I like the idea to configure headers via hostrule |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
We'd like this for being able to access the snapcraft api |
Beta Was this translation helpful? Give feedback.
-
Tell us more.
Describe the proposed change(s).
Certain endpoints require special auth header to access the correct content. An example, and my use case is to retrieve the plex version. Without a
X-Plex-Tokenheader, plex's apihttps://plex.tv/api/downloads/5.jsonreturns only stable versions. With the header the api returns beta versions instead (which is the behavior I would like).Beta Was this translation helpful? Give feedback.
All reactions