-
Notifications
You must be signed in to change notification settings - Fork 714
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds rationale and notes around comma-separated HTTP headers #1205
Conversation
@@ -60,6 +60,15 @@ attempting to do that would limit the applicability of Brave, which is an anti- | |||
goal. Instead, we choose to use nothing except floor Java version features, | |||
currently Java 6. | |||
|
|||
Here's an example of when things that seem right aren't. We once dropped our |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is not about HTTP, but don't feel like moving it to another PR ...
responsibility of the `Propagation` implementation. Hence, the `Injector`, | ||
which knows format rules, should do comma joining when valid. | ||
|
||
Some think that sending a header in comma-separated format, implies a receiver |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I added this point because it is a common fantasy
Thanks for the help @NersesAM ! |
No description provided.