Support HEAD method for healthcheck

[mrchypark]

It would be beneficial for the healthcheck endpoint to support the HEAD HTTP method. Here are some reasons why:

The HEAD method is similar to GET, but it only retrieves the headers of the response without the response body. This makes it lightweight and efficient for checking the status of a resource without transferring unnecessary data.

Compliance with HTTP standards: Supporting the HEAD method adheres to the HTTP specification, which states that any resource that supports GET should also support HEAD. This ensures better compatibility and interoperability with clients and tools that expect HEAD support.

Faster response times: Since the HEAD method doesn't require the server to generate and send the response body, it can lead to faster response times compared to using GET for healthcheck. This can be important in latency-sensitive environments or when dealing with a high volume of healthcheck requests.

Consistency with other endpoints: If other endpoints in the application already support the HEAD method, having the healthcheck endpoint also support it maintains consistency and follows the principle of least astonishment for developers and users interacting with the API.

Supporting the HEAD method for the healthcheck endpoint aligns with best practices, improves efficiency, and enhances the overall user experience of the application.
Please let me know if you have any further questions or if there's anything else I can assist with.

[nitisht]

Thanks @mrchypark this makes sense. We'll add the support soon.