Fix Content-Type for ActivityPub requests #1987
Conversation
Register appropriate responders to handle activity+json and ld+json requests from other fediverse in the ActivityPubController. Signed-off-by: Dave MacFarlane <driusan@gmail.com>
driusan
force-pushed
the
FixContentType
branch
from
5c5827d to
cfff2ca
Compare
|
Hello there, We hope that the review process is going smooth and is helpful for you. We want to ensure your pull request is reviewed to your satisfaction. If you have a moment, our community management team would very much appreciate your feedback on your experience with this PR review process. Your feedback is valuable to us as we continuously strive to improve our community developer experience. Please take a moment to complete our short survey by clicking on the following link: https://cloud.nextcloud.com/apps/forms/s/i9Ago4EQRZ7TWxjfmeEpPkf6 Thank you for contributing to Nextcloud and we hope to hear from you soon! (If you believe you should not receive this message, you can add yourself to the blocklist.) |
1 participant
I was not able to find my nextcloud social account with any of my other fediverse accounts because the Content-Type header sent by the server does not match the ActivityPub spec.
This updates the ActivityPubController to register a responder for
application/ld+json; profile="https://www.w3.org/ns/activitystreams"(defined by the AP spec and used by Mastodon) as well asapplication/activity+json(also considered valid by the spec and used by misskey/sharkey/etc) according to the Accept header of the request.I believe this fixes #1734. (For me webfinger was working, but other AP servers are discarding the response when trying to retrieve the profile because of the incorrect Content-Type header.)