Skip to content

Enabling baggage cache to support limits and non-ascii characters - #8713

Merged
mhlidd merged 7 commits into
masterfrom
mhlidd/update_baggage_limits
May 7, 2025
Merged

mhlidd merged 7 commits into
masterfrom
mhlidd/update_baggage_limits

Conversation

@mhlidd

@mhlidd mhlidd commented Apr 21, 2025 •

Copy link
Copy Markdown
Contributor

What Does This Do

Previously, the Baggage Cache implemented injected incoming headers if no modification to baggage was made while ignoring limits. In order to be in compliance with limits, this PR adds support to truncate the baggage cache if limits are violated. Furthermore, Java does not support sending non-ascii characters in http headers. This PR also forcefully builds a outgoing baggage header if the incoming header includes non-encoded non-ascii characters by disabling the cache when extracting such headers.

Motivation

Additional Notes

Verified through unit tests and system-tests in test_baggage.py.

Contributor Checklist

Jira ticket: [PROJ-IDENT]

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

comp: api Tracer public API type: feature Enhancements and improvements

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants