Add header support when using custom request url #734
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A more generalized version of #660 that allows arbitrary headers to be specified when using a custom
requestUrl
. It determines the headers at request time so that values can be specified dynamically.Our use case is adding an Authorization header to proxied Google requests. The custom proxy allows us to append the Google API key server side so it is not exposed via app traffic (as we can not use a restricted key with this library). We also need to guard against unauthorized usage of the proxy.
Example usage: