HttpLoader: Suppress HTTP Content-Type validation about titanium-json-ld HOT 6 CLOSED

JSON-LD 1.1 specification is quite strict on how to deal with content type that does not represent the content.

6. Otherwise, the retrieved document's Content-Type is neither application/json, application/ld+json, nor any other media type using a +json suffix as defined in [RFC6839]. Reject the promise passing a loading document failed error.

9.4.1. LoadDocumentCallback

FYI: Jena does not support JSON-LD 1.1 but 1.0

You can download the content on your side or you can implement an interceptor replacing wrong content type header.

from titanium-json-ld.

The spec. is indeed clear, but a Feature can be an extension to the spec. , as Playground does ( silently , which is not good ).
I mean, an explicit option could be set in the API, plus a warning at runtime.

from titanium-json-ld.

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

from titanium-json-ld.

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

from titanium-json-ld.

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days

from titanium-json-ld.

Since 1.1.0 you can create your own instance of HttpLoader and set fallback content type.

e.g.

HttpLoader lodaer = new HttpLoader(DefaultHttpClient.defaultInstance());
loader.setFallbackContentType(MediaType.JSON);
...
options.setDocumentLoader(loader);

from titanium-json-ld.