Closed eroux closed 6 years ago
fetching a .json gets a content-type header turtle, example:
± curl -v -sSL http://buda1.bdrc.io:13280/resource/G844.json -o /dev/null * Trying 52.21.222.115... * TCP_NODELAY set * Connected to buda1.bdrc.io (52.21.222.115) port 13280 (#0) > GET /resource/G844.json HTTP/1.1 > Host: buda1.bdrc.io:13280 > User-Agent: curl/7.58.0 > Accept: */* > < HTTP/1.1 200 OK < Server: Apache-Coyote/1.1 < Access-Control-Allow-Origin: * < Access-Control-Allow-Headers: origin, content-type, accept, authorization < Access-Control-Allow-Credentials: true < Access-Control-Allow-Methods: GET, POST, PUT, DELETE, OPTIONS, HEAD < Content-Type: text/turtle;charset=utf-8 < Transfer-Encoding: chunked < Date: Mon, 30 Apr 2018 13:34:23 GMT
The content-type should be application/json. I didn't test other possibilities, but I guess a few tests would be good...
application/json
Fixed !
fetching a .json gets a content-type header turtle, example:
The content-type should be
application/json
. I didn't test other possibilities, but I guess a few tests would be good...