-
Notifications
You must be signed in to change notification settings - Fork 70
Allow users to supply arbitrary HTTP headers for requests #239
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
cc @ryanslade as a sanity check to ensure that this isn't undoing any work in deprecating non-envvar settings. |
garobrik
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Co-authored-by: Stephen Gutekanst <stephen.gutekanst@gmail.com>
emidoots
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice work
mrnugget
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice! Left some comments regarding documentation of this feature.
mrnugget
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.

Closes #238.
This threads header values into the HTTP calls to the Sourcegraph instance via envvars such as
SRC_HEADER_FOO=BAR(whereFoo: barwould be the additional header value - note that header names are case insensitive).This is applied to:
This is notably to fix a particular customer's issue, which has their instance behind an authenticating proxy that accepts special bearer tokens.