Mimetype not registered #5
You are producing a MIME-type without having registered it properly,
Please don't hijack names like that, especially not if you ignore the commonly provided
x- registration-free prefixes. It's unpolite and leads to a chaos of undocumented names if standards are ignored or overruled. The interference is minimised and interoperability maximised with a simple registration of the name and a specification. In this case, it's a web form and you may get some email interaction.
Thanks, good point, we will take this up as a possible enhancement for future versions. When producing results, the standard
application/json may actually be fine for Searsia. However -- you may find this even more inpolite -- mimetypes are also used internally to decide on strategies to parse results from disparate, federated sources, see the searsiaserver code: It has totally nonsensical mimetype
application/html+json, because one of our clients returned html code inside json strings, because, why not?
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?