Outgoing Content-Type is not scoped #127
Assignees
Labels
area:code
Affects or applies to the library code
good first issue
Good for newcomers
type:bug
Something isn't working
Comments
warriordog
added
type:bug
|
I'll pick this one up and work on it |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
According to the spec, the acceptable content types are:
application/ld+json; profile="https://www.w3.org/ns/activitystreams"application/activity+jsonThe latter type is described as optional, and implementations are not required to support it.
For best results, it's recommended to accept either form but use the first for outgoing requests.
Our implementation currently supports only the second, unscoped type along with these extra types for maximum compatibility:
application/activity+jsonapplication/ld+jsonapplication/jsonThis works against all tested Fedi implementations, but we should include the profile for better spec-compliance. This may require a refactor of
ActivityPubOptions.See also: https://www.w3.org/TR/activitypub/#client-to-server-interactions
The text was updated successfully, but these errors were encountered: