fix: expose healthcheck API as public endpoint

[mr-karan]

Fixes #380

If basic auth is enabled, the endpoint will still respond with 200.

curl -i localhost:9000/api/health
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Date: Wed, 02 Jun 2021 14:38:47 GMT
Content-Length: 14

{"data":true}

[knadh]

hm, this would make /api/health an exception to the /api/* path which is meant to be private, complicating writing firewall and proxy rules.

How about we retain the old /api/health for backwards compatibility (and deprecate it) and add a new public handler, /health?

[mr-karan]

path which is meant to be private, complicating writing firewall and proxy rules.

Makes sense.

How about we retain the old /api/health for backwards compatibility (and deprecate it) and add a new public handler, /health?

Made the changes.

❯ curl -i localhost:9999/health localhost:9999/api/health
HTTP/1.1 200 OK
Content-Type: application/json; charset=UTF-8
Date: Thu, 03 Jun 2021 05:53:27 GMT
Content-Length: 14

{"data":true}
HTTP/1.1 401 Unauthorized
Content-Type: application/json; charset=UTF-8
Www-Authenticate: basic realm=Restricted
Date: Thu, 03 Jun 2021 05:53:27 GMT
Content-Length: 27

{"message":"Unauthorized"}