search

hvdsomp / signposting

7 stars 0 forks source link

Default response for .well-known/api-catalog #26

Closed huberrob closed 7 months ago

huberrob commented 7 months ago

Should a request on .well-known/api-catalog immediately deliver the JSON content by default? This would avoid the extra request.

By now the spec just indicates the returned header but not the content. In draft-ietf-httpapi-api-catalog it is defined to deliver the JSON for a Accept: application/linkset+json but not if the Accept type is not defined Is it OK to deliver the JSON by default?

Basic example: https://f-uji.net/.well-known/api-catalog (just showing the header, empty json)

hvdsomp commented 7 months ago

The api-catalog spec says the well-known URI should resolve to the catalog document. So, that could mean directly deliver, redirect, etc. But in the end, one ends up at the actual document. Since we only define a single document format, access without mime type information should by default return the application/linkset+json.

hvdsomp commented 7 months ago

Basic example: https://f-uji.net/.well-known/api-catalog (just showing the header, empty json)

This should have an api-catalog link in the Link header ;-)

huberrob commented 7 months ago

still puzzling with the .htaccess should be there now..

hvdsomp commented 7 months ago

@huberrob can this issue be closed? or do you have further observations?