Skip to content

Conversation

mikewest
Copy link
Member

@mikewest mikewest commented Oct 14, 2025

Signature-based Integrity 1 relies on user agents properly handling Unencoded-Digest headers 2 which deliver a server's assertions about the integrity of a given response's body.

This patch extracts the relevant algorithms from 1, spelling out the processing model for the header, and verifying response integrity at the end of Main Fetch, alongside SRI's existing check.

This is one step of the Signature-based Integrity upstreaming work detailed in 3.

(See WHATWG Working Mode: Changes for more details.)


Preview | Diff

Signature-based Integrity [1] relies on user agents properly handling
`Unencoded-Digest` headers [2] which deliver a server's assertions about
the integrity of a given response's body.

This patch extracts the relevant algorithms from [1], spelling out the
processing model for the header, and verifying response integrity at the
end of Main Fetch, alongside SRI's existing check.

This is one step of the Signature-based Integrity upstreaming work
detailed in [3].

[1]: https://wicg.github.io/signature-based-sri/
[2]: https://httpwg.org/http-extensions/draft-ietf-httpbis-unencoded-digest.html
[3]: WICG/signature-based-sri#49.
@mikewest
Copy link
Member Author

Hey folks! I'd like to start upstreaming signature-based integrity checks; this seemed like the simplest self-contained place to start. Assuming folks are on board, I'll file implementation and MDN bugs, and put up more PRs against SRI and CSP.

cc @annevk @mozfreddyb

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant