From 50d861e70825653f060dcf1be5204a3733b377d6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Joakim=20Br=C3=A4nnstr=C3=B6m?= Date: Mon, 6 Jul 2026 14:46:14 +0200 Subject: [PATCH] Update tracestate example for header format Clarified example of tracestate header formatting to ensure only the most recent position is included. --- spec/20-http_request_header_format.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spec/20-http_request_header_format.md b/spec/20-http_request_header_format.md index a0d6866..cb3f526 100644 --- a/spec/20-http_request_header_format.md +++ b/spec/20-http_request_header_format.md @@ -320,7 +320,7 @@ Example: `vendorname1=opaqueValue1,vendorname2=opaqueValue2` Tracing tools are not supposed to add the same header multiple times. For example, if a vendor name is Congo and a trace started in their system and then went through a system named Rojo and later returned to Congo, the `tracestate` value would not be: -`congo=congosFirstPosition,rojo=rojosFirstPosition,congo=congosSecondPosition` +`congo=congosSecondPosition,rojo=rojosFirstPosition,congo=congosFirstPosition` Instead, the entry would be rewritten to only include the most recent position: `congo=congosSecondPosition,rojo=rojosFirstPosition`