Add device bound session credentials headers#29161
Merged
Conversation
Contributor
|
Tip: Review these changes grouped by change (recommended for most PRs), or grouped by feature (for large PRs). |
Elchi3
approved these changes
Mar 3, 2026
Member
Elchi3
left a comment
There was a problem hiding this comment.
Thanks Daniel! 👍
("Sec-Secure" -- okay?!)
Contributor
Author
Nobody pays me to name these things. I wish they would! 🫠 |
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
2 participants
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
This adds features for the request and response headers from the Device Bound Session Credentials (DBSC) spec.
Test results and supporting details
I took the version numbers from the rollout steps in the Chrome Platform Status entry. Vendor commentary on this feature in web-features led me to believe this is accurate.
Related issues