UN http server missing content-type for json-ld context on GET request

[Fak3]

Currently UN json-ld context located at https://service.unece.org/trade/uncefact/vocabulary/uncefact.jsonld and on GET request the server responds with empty content-type header:

u1@linux-fdsk:~> curl -I https://service.unece.org/trade/uncefact/vocabulary/uncefact.jsonld
HTTP/1.1 200 OK
Date: Tue, 18 May 2021 11:45:21 GMT
Last-Modified: Sun, 18 Apr 2021 08:22:52 GMT
ETag: "29bd50-5c03aeb4ecf00"
Accept-Ranges: bytes
Content-Length: 2735440
Strict-Transport-Security: max-age=157680000; includeSubDomains

Json-ld playground and possibly other json-ld processing libararies require that the server responds with proper content-type header "application/json" or "application/ld+json". So right now the UN context url can't be recognized as valid json-ld context.

Side note: the edi3 server, where the context file was prevoiusly hosted, has the correct header:

u1@linux-fdsk:~> curl -I https://edi3.org/vocabulary/uncefact-context.jsonld
HTTP/2 200 
server: GitHub.com
content-type: application/ld+json
...

[Fak3]

Ah, this is probably duplicate of #48