Unrecognised relations in Content-Type interferes with content negotiation

[csarven]

curl -iH'Accept: application/ld+json' https://csarven.solid.community/public/
HTTP/1.1 200 OK
Content-Type: application/ld+json

curl -iH'Accept: application/ld+json; profile="https://www.w3.org/ns/activitystreams"' https://csarven.solid.community/public/
HTTP/1.1 200 OK
Content-Type: text/turtle

See also:

curl -iH'Accept: application/ld+json; profile=""' https://csarven.solid.community/public/
Content-Type: application/ld+json

curl -iH'Accept: application/ld+json; profile="x"' https://csarven.solid.community/public/
Content-Type: text/turtle

curl -iH'Accept: application/ld+json; x=""' https://csarven.solid.community/public/
Content-Type: application/ld+json

curl -iH'Accept: application/ld+json; x="y"' https://csarven.solid.community/public/
Content-Type: text/turtle

The server should at the very least ignore the relations it can't handle and return application/ld+json, or return 406.

[rubensworks]

This may be fixed already in eb73ae2aa6f1477b3b11bb681484eff43f5a6302 (v5.0.0), to be tested.

[kjetilk]

OK, cool, I created a retest label to remind us about this. :-)

[angelo-v]

The current behaviour is:

▶ curl -iH'Accept: application/ld+json; profile="https://www.w3.org/ns/activitystreams"' https://angelo.veltens.org/profile/actor     
HTTP/2 406 

Cannot serve requested type: application/ld+json

Which is "funny", because https://angelo.veltens.org/profile/actor actually is a JSON-LD document containing an activity streams actor.

Fixing this would be a step forward in beeing complient to ActivityPub, see https://socialhub.activitypub.rocks/t/problems-posting-to-mastodon-inbox/801/8