- From: W3C Webmaster via GitHub API <noreply@w3.org>
- Date: Tue, 24 Jun 2025 17:00:46 +0000
- To: public-trace-context@w3.org
- Message-Id: <E1uU70o-00CnJE-06@janus.w3.internal>
Issues ------ * w3c/trace-context (+0/-0/💬1) 1 issues received 1 new comments: - #438 How to preserve trace context on http redirect ? (1 by Mart-Bogdan) https://github.com/w3c/trace-context/issues/438 * w3c/correlation-context (+0/-2/💬0) 2 issues closed: - Discussion: Should we drop the requirement to percent-encode values of list-members https://github.com/w3c/baggage/issues/145 - Clarify how compliant implementations should handle invalid baggage entries https://github.com/w3c/baggage/issues/137 Pull requests ------------- * w3c/correlation-context (+0/-2/💬0) 2 pull requests merged: - clarify encoding rules for property values https://github.com/w3c/baggage/pull/148 - Clarify that the behavior for handling invalid baggage string values is undefined https://github.com/w3c/baggage/pull/147 Repositories tracked by this digest: ----------------------------------- * https://github.com/w3c/trace-context * https://github.com/w3c/correlation-context * https://github.com/w3c/distributed-tracing-wg -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 June 2025 17:00:46 UTC