The manner for getting the context has been updated. Note the link header use as an option (?) for resolving the context. We may not be able to simply content negotiate, we will need to look for the link header too.
Further info.. related to schema.org recently dropped support for content negotiation. They instead adopted a Link header, with rel="alternate" and type="application/ld+json".
So schema.org headers will be like:
access-control-allow-credentials: true
access-control-allow-headers: Accept
access-control-allow-origin:
l ink: </docs/jsonldcontext.jsonld>; rel="alternate"; type="application/ld+json"
Due to: https://github.com/schemaorg/schemaorg/issues/2578
The manner for getting the context has been updated. Note the link header use as an option (?) for resolving the context. We may not be able to simply content negotiate, we will need to look for the link header too.