Add typed ECT request Client Hint metadata - #960
Open
fewensa wants to merge 1 commit into
Open
Conversation
codeon:
version: 1
authority: FWN-348
description: |-
Parse and emit singleton ECT Client Hint values with Network Information tokens through the existing DPR-style typed metadata path, including client emit, server parse accessors, focused tests, and brief README coverage.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ECTrequest Client Hint parsing and emission (slow-2g/2g/3g/4g) following the existing DPR metadata pattern.Test plan
cargo test -p rttp-protocol --test client_hintscargo test -p rttp_client --test test_raw_request_capture ect_helpercargo test -p rttp-server --test metadata_facade request_facade_parses_ect