Provide JSON for user agent curl

[acka47]

When looking up a concept URI with curl I expect to get back JSON but I do get HTML.

Example:

$ curl -LI "https://w3id.org/kim/hcrt/drill_and_practice"
HTTP/1.1 302 Found
Date: Wed, 17 Jan 2024 11:19:32 GMT
Server: Apache/2.4.29 (Ubuntu)
Access-Control-Allow-Origin: *
Location: https://skohub.io/dini-ag-kim/hcrt/heads/master/w3id.org/kim/hcrt/drill_and_practice
Content-Type: text/html; charset=iso-8859-1

HTTP/1.1 200 OK
Date: Wed, 17 Jan 2024 11:19:32 GMT
Server: Apache/2.4.52 (Ubuntu)
Content-Location: drill_and_practice.en.html
Vary: negotiate,accept,accept-language,Accept-Encoding
TCN: choice
Last-Modified: Wed, 10 Jan 2024 13:20:47 GMT
ETag: "4c4a-60e974c90c064;60e974c912dc4
Accept-Ranges: bytes
Content-Length: 19530
Access-Control-Allow-Origin: *
Content-Type: text/html; charset=UTF-8
Content-Language: en

We should configre the webserver as for lobid where I do get JSON with the default user agent set by curl. It probably makes sense to just copy the respective web server config from lobid.

[sroertgen]

We should also document this configuration as an example in the README

[Phu2]

In order to get json you should provide the request header: curl -L "https://w3id.org/kim/hcrt/drill_and_practice" -H "Accept: application/json". I don't think it is a good idea to rely on the user agent.
As for lobid i haven't found any web server config in this regard.

[sroertgen]

@acka47 we just found out that this now works after merging skohub-io/skohub-vocabs#279

We think this is because Apache is not trying to parse languages anymore, since Content-Language: en is not present anymore in the header.

Closing this now.

[Phu2]

For clarification: curl sends per default Accept: */* (as one can see using the -v option)