Relative location of ping endpoint

[mskyttner]

When reverse proxying a container running duckdb 1.2.0 w httpserver 0.1.15 with a base_path setting such as "/custom/", I noticed that the ping endpoint is absolute and not relative to the base_path.

This would be nice to have (endpoints relative to the base_path) because it would allow placing the service as a complete "subtree" alongside with other services more easily under the same (sub)domain name.

[lmangani]

So sorry for the huge delay and hopefully you still need this. Implemented in #40

[mskyttner]

Wow, so nice! It is so useful to this endpoint located "in the tree" so the "webroot" can be free if running multiple instances served from the same web root context through a reverse proxy.

That one would be nice to have unauthenticated access against, for liveness checks that may can just do a HEAD request without having to carry credentials to get a 200.

[lmangani]

That one would be nice to have unauthenticated access against, for liveness checks that may can just do a HEAD request without having to carry credentials to get a 200.

Not sure about this one, but if you want please open a PR or new Issue and we'll add an option for it. Thanks!