<![CDATA[I (hopefully) made some progress regarding HTTPS signature handling and double-knocking.]]>I (hopefully) made some progress regarding HTTPS signature handling and double-knocking.

Current default is to first try draft-cavage-http-signatures-12, then RFC 9421: HTTP Message Signatures. This may be changed later.

Retry (the second knock) is done, if the first results in a 400, 401 or 403.

If the peer instance has accepted DC12 in the past, the double-knocking will use DC12 first, then RFC9421.

If the peer instance has accepted RFC9421 in the past, the double-knocking will use RFC9421 first, then DC12.

]]>https://bb.devnull.land/topic/f7f57223-f351-4427-a280-c0225f798ebd/i-hopefully-made-some-progress-regarding-https-signature-handling-and-double-knocking.RSS for NodeMon, 14 Sep 2026 03:37:24 GMTSat, 12 Sep 2026 20:11:02 GMT60<![CDATA[Reply to I (hopefully) made some progress regarding HTTPS signature handling and double-knocking. on Sun, 13 Sep 2026 00:45:04 GMT]]>@nick@mammuthus.de shouldn't the double knock be 9421 first, and then cavage-12 on failure?

Also cool! I'd love to test NodeBB's implementation against it. <img class="not-responsive emoji" src="/emoji/ap/smile/activitypub.space" title="😄" />

]]>https://bb.devnull.land/post/https://activitypub.space/post/2448https://bb.devnull.land/post/https://activitypub.space/post/2448Sun, 13 Sep 2026 00:45:04 GMT