Feature Request: allow health check endpoint to respond to HEAD requests

[james2doyle]

I'm currently using that endpoint to check the status of my server on Pockethost. Currently, it looks like /api/health will respond to HEAD requests with 404.

I think it would be ideal if it just responded with a 2xx code instead of 404. And ideally an empty body.

[motdde]

Hello @james2doyle ,

Would there be a specific use case where the current GET request wouldn't be the ideal (work as intended)?

[james2doyle]

I'm using a 3rd party package to check for an Internet connection in a Flutter app. Basically the plug-in checks an array of given URLs on an interval. One of the URLs I added to check was the health endpoint. But because that endpoint can't respond to a HEAD request, it returns a 404. Which is not in the 200 range and it's considered an error. Ideally a HEAD request would return an empty body. Unless a range header was specified. And so it can be a lightweight way to check if the server is up. Does that make sense? Sorry if it's a bit convoluted

…

On Thu, Feb 8, 2024, 5:02 PM Oluwaseun Oyebade ***@***.***> wrote: Hello @james2doyle <https://github.com/james2doyle> , Would there be a specific use case where the current GET request wouldn't be the ideal (work as intended)? — Reply to this email directly, view it on GitHub <#4310 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAK37GGT4ZHY4XQFHHZVO4DYSVYQPAVCNFSM6AAAAABC65G7OKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZVGE3TAMBSG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[ganigeorgiev]

Support for HEAD /api/health was added in master and it will be available with the next minor release.