Broaden accepted values in non-urlencoded headers #4132
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After open-telemetry#4103 we accept non url-encoded headers for OTLP. Naively this implementation only accepts digits, ascii letters, underscores (\w) and spaces. Instead broaden the accepted chars to what we accept for urlencoded values so that we accepts = to allow for base64 encoded values.
lzchen
approved these changes
Aug 19, 2024
|
Probably can include a CHANGELOG |
This is a fix for a feature still unreleased with already an entry in the CHANGELOG |
hyoinandout
pushed a commit
to hyoinandout/opentelemetry-python
that referenced
this pull request
Aug 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
After #4103 we accept non url-encoded headers for OTLP. Naively this implementation only accepts digits, ascii letters, underscores (\w) and spaces. Instead broaden the accepted chars to what we accept for urlencoded values so that we accepts = to allow for base64 encoded values.
Refs #4103
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Does This PR Require a Contrib Repo Change?
Checklist: