Skip to content

Use server-timing for trace context response#560

Merged
SergeyKanzhelev merged 4 commits intow3c:mainfrom
dynatrace-oss-contrib:server-timing-response
Oct 20, 2025
Merged

Use server-timing for trace context response#560
SergeyKanzhelev merged 4 commits intow3c:mainfrom
dynatrace-oss-contrib:server-timing-response

Conversation

@dyladan
Copy link
Copy Markdown
Member

@dyladan dyladan commented Feb 27, 2024

This is a first draft of the server-timing response header. It is not meant to be a final version, but a place to start discussion. It is mostly a direct translation with the following exceptions:

Version is optional

In the original version, all fields were required in order to simplify parsing. Now that we are a small component of a more complex header, that simplicity is lost, and the parsing simplification is no longer beneficial.

Flags are optional

The reasoning is the same as above. Additionally, some servers may not want to reveal information like the sampled flag to an untrusted client in order to avoid abuse.

Terminology Fixes

Changed ambiguous or nonstandard terms like "callee" and "caller" to established terms like "server" and "client."


Preview | Diff

@dyladan dyladan marked this pull request as ready for review August 26, 2025 20:14
@SergeyKanzhelev SergeyKanzhelev merged commit d3634b2 into w3c:main Oct 20, 2025
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants