Problem
Overland currently supports sending an access token via the Authorization: Bearer header, which is great. However, there's no way to add arbitrary custom HTTP headers to requests.
This is a blocker for users who run their backend behind reverse proxies or zero-trust solutions that require additional headers for authentication. A common example is Cloudflare Access / Zero Trust, which expects two service token headers on every request:
CF-Access-Client-Id: <value>
CF-Access-Client-Secret: <value>
Proposed Solution
Add a configurable list of custom HTTP headers (key/value pairs) in the Server URL settings screen, alongside the existing endpoint URL, device ID, and access token fields. These headers would be included on every POST request to the server.
This keeps it generic rather than tied to any specific provider, users could use it for Cloudflare Access, Authelia, Authentik, custom API gateways, or any other setup that requires extra headers.
The overland://setup custom URL scheme could also be extended to support this, e.g.:
overland://setup?url=...&token=...&header_CF-Access-Client-Id=xxx&header_CF-Access-Client-Secret=yyy
PR In Progress
I'm working on a PR for this right now, adding a configurable list of custom header key/value pairs to the Server URL settings, included on every outgoing request. Will mention this issue once it's ready for review.
Problem
Overland currently supports sending an access token via the
Authorization: Bearerheader, which is great. However, there's no way to add arbitrary custom HTTP headers to requests.This is a blocker for users who run their backend behind reverse proxies or zero-trust solutions that require additional headers for authentication. A common example is Cloudflare Access / Zero Trust, which expects two service token headers on every request:
Proposed Solution
Add a configurable list of custom HTTP headers (key/value pairs) in the Server URL settings screen, alongside the existing endpoint URL, device ID, and access token fields. These headers would be included on every POST request to the server.
This keeps it generic rather than tied to any specific provider, users could use it for Cloudflare Access, Authelia, Authentik, custom API gateways, or any other setup that requires extra headers.
The
overland://setupcustom URL scheme could also be extended to support this, e.g.:PR In Progress
I'm working on a PR for this right now, adding a configurable list of custom header key/value pairs to the Server URL settings, included on every outgoing request. Will mention this issue once it's ready for review.