Skip to content

Conversation

@mjankowski
Copy link
Contributor

Resolves #1431

This page was actually improved quite a bit since the original issue, but I think the nuance around this one detail is still missing. This is essentially a verbatim copy/paste from the issue into what I think is a relevant portion of the spec description/guide.

I contemplated whether this was most appropriate on this security page or the AP spec page, and opted for here. Don't feel strongly though, could move.

@andypiper
Copy link
Member

Requesting an additional review from @oneiros or @ClearlyClaire just to double-check here, thanks.

@mjankowski mjankowski force-pushed the journey-of-keyid-and-actor-fragment-vs-whole-hog branch from 0cc1bc3 to 656b99f Compare November 30, 2025 16:49
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.

Document HTTP Signature keyId algorithm when the keyId points to either an actor or to a key

2 participants