On Thu, 10 Feb 2022, Willy T. Koch wrote:
…and calling it as a webservice with Postman/curl.
Ah, I think we might not be exposing the full details of the mime types
via the server, only details of their parsers and the heirarchy, eg
http://localhost:9998/mime-types#audio/vorbis
(We have that info in Java we're just seemingly not making it available)
I'm not sure about exposing all the details of all the types by default,
but adding a flag and/or a sub-endpoint that would return the full details
of a type, including extensions and comments etc, seems OK to me. Thoughts
anyone?
Nick
