I was really confused why when I made requests to wafrn URLs I was getting HTML back. At first I thought maybe it was a 404, but, no, wafrn instances are returning 200 responses despite my Accept header requesting ActivityPub content.So apparently, if wafrn requires a signed request to /fediverse/post/:id/ or /fediverse/blog/:url/outbox, and if the request is either not signed or use RFC-9421, then wafrn will respond with a 200 text/html representation of the content.And, also... Strangely...My requests to collection endpoints (even /fediverse/post/:id/replies) do respond correctly.I do appreciate implementations that return HTTP error responses (401, 403, and 406). It allows me to catch the error and try again until all signature types are exhausted (RFC-9421 first, then cavage-12). But I guess now, in order to workaround wafrn behavior, I cannot assume a 200 is a successful response and will resend the request if the Content-Type is not ActivityPub content.And this behavior also confuses browser.pub.
