Propagators should support all forms of Instana Headers #29
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.
Depending on where
Inject
andExtract
are being called from, the HTTP headers can vary in capitalization and prefix.For example, in Flask and Django, in the middleware, HTTP headers are presented as all upper case, underscores and prefixed with
HTTP_
(Ruby also does this in Rack):HTTP_X_INSTANA_T
Yet in making requests via the
requests
package, HTTP headers are in the on-the-wire format:X-Instana-T
Our propagators should support all variations:
HTTP_
for now)