You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
## Summary of changes
When parsing a `baggage` header, if it is malformed in any way, ignore the entire header instead of trying to extract the valid key/value pairs.
## Reason for change
This is the defined behavior in the RFC and how we implement baggage in other tracing libraries.
## Implementation details
Bail our as soon as we find any invalid format in the `baggage` header.
## Test coverage
Fixed existing tests and added more test cases.
## Other details
n/a
<!-- Fixes #{issue} -->
<!-- ⚠️ Note: where possible, please obtain 2 approvals prior to merging. Unless CODEOWNERS specifies otherwise, for external teams it is typically best to have one review from a team member, and one review from apm-dotnet. Trivial changes do not require 2 reviews. -->
{"key1=value1, key2 = value2;property1;property2, key3=value3; propertyKey=propertyValue",[("key1","value1"),("key2","value2"),("key3","value3")]},// W3C metadata/property not currently supported so the values are discarded
0 commit comments