Allow custom headers for self-hosted instances #2227
jeankhawand
started this conversation in
Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary
Add support for configuring custom HTTP headers when connecting to self-hosted instances.
Problem
Some self-hosted deployments sit behind a reverse proxy, authentication gateway, API gateway, or zero-trust solution that requires additional HTTP headers on every request.
If the client only supports the instance URL and standard authentication, these deployments may be unreachable even though the underlying service is fully compatible.
Example use case
A company hosts an instance behind an access proxy such as Cloudflare Access, an API gateway, or another authentication layer.
Requests may require additional headers such as:
Or more generally:
Without support for custom headers, users may need to:
Proposed solution
Allow optional custom headers to be configured for self-hosted instances.
For example:
These headers should be included in requests made to the configured instance.
Ideally, sensitive header values should support environment variables or another secret-storage mechanism rather than requiring plaintext secrets in configuration.
Why this is important
Custom authentication and proxy headers are common in enterprise and security-conscious self-hosted environments.
Supporting custom headers would allow self-hosted instances to work with existing access-control infrastructure without requiring users to modify or weaken their network architecture.
It also keeps the feature generic rather than requiring provider-specific integrations for Cloudflare Access, API gateways, reverse proxies, or other authentication systems.
All reactions