Remove custom header name for Baggage, use official header #993
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
arminru
approved these changes
Sep 23, 2020
This comment has been minimized.
This comment has been minimized.
SergeyKanzhelev
approved these changes
Sep 23, 2020
Signed-off-by: Bogdan Drutu <bogdandrutu@gmail.com>
bogdandrutu
force-pushed
the
baggageprop
branch
from
9afeb73
to
9370220
Compare
carlosalberto
approved these changes
Sep 23, 2020
arminru
reviewed
Sep 24, 2020
Co-authored-by: Armin Ruech <armin.ruech@dynatrace.com>
|
@bogdandrutu Please add a changelog entry and a spec compliance matrix entry to keep track of implementations adopting the change. |
This pull request was closed.
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.
Fixes #879
Changes
During the w3c meeting there was a consensus to use the current w3c baggage definition, and avoid using a custom header name.