Open thbar opened 3 years ago
The encoding is also not set as a header, leading to this output on some browsers:
It would be a good idea to fix this at the same time, with a Content-Type: application/json; charset=utf-8
(but maybe just switching to JSON) will correct that as well, actually.
During my manual tests of #109, I noticed that when the base schedule is not available, we get a
text/plain
error currently.Here is an example, using a local test config and querying
http://localhost:8080/test
:Since the whole API is JSON, I believe standardising on JSON content-type of errors would be better for the end-user life.
Useful resources