<![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://forum.pierobosio.it/topic/e563400d-1c68-462a-a772-5ccf717a3e8d/i-hopefully-made-some-progress-regarding-https-signature-handling-and-double-knocking.RSS for NodeMon, 14 Sep 2026 14:41:16 GMTSat, 12 Sep 2026 20:11:02 GMT60<![CDATA[Reply to I (hopefully) made some progress regarding HTTPS signature handling and double-knocking. on Mon, 14 Sep 2026 08:34:04 GMT]]>@julian@activitypub.space

Needs more testing... before RFC9421 could be used first... 😉

Improving compatibility would be nice.

Afair i have already seen a NodeBB message using RFC9421, that was successfully verified.

]]>https://forum.pierobosio.it/post/https://mammuthus.de/users/nick/notes/1009https://forum.pierobosio.it/post/https://mammuthus.de/users/nick/notes/1009Mon, 14 Sep 2026 08:34:04 GMT<![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="https://activitypub.space/assets/plugins/nodebb-plugin-emoji/emoji/android/1f604.png?v=5a9b4bf9c7f" title=":smile:" />

]]>https://forum.pierobosio.it/post/https://activitypub.space/post/2448https://forum.pierobosio.it/post/https://activitypub.space/post/2448Sun, 13 Sep 2026 00:45:04 GMT