add configuration option for additional request headers #96
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.
Pull Request
Related issue
none
What does this PR do?
We're using scrapix to index our documentation.
Some parts of the documentation are protected, so we need a way to send some authentication information with the crawler requests.
This PR adds a new configuration property
additional_request_headers
which are applied to each request in a pre navigation hook.This way we're able to either send an
Authorization
header (basic, bearer etc.) or a custom auth header (e.g.x-access-key
), so it should be quite flexible for any usecase.