You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the existing issues for similar feature requests.
I added a descriptive title and summary to this issue.
Summary
Implementing support for the HTTP HEAD method for the /healthz endpoint enhances efficiency and reduces bandwidth usage by allowing quick retrieval of metadata about the service's health without sending the entire response body.
This aligns with HTTP standards, improves monitoring capabilities, and contributes to the scalability and reliability of the system.
Why?
I wanted to add support for the HTTP HEAD method to the /healthz endpoint because I wanted to integrate it with my monitoring service, which only supports HEAD requests. Upon further consideration, I realized the benefits it offers. Specifically, it enhances efficiency by allowing quick retrieval of metadata about the service's health without transmitting the entire response body, reducing bandwidth usage. Additionally, supporting this method aligns with HTTP standards, improves monitoring capabilities, and contributes to the scalability and reliability of the system.
How?
Adding support for the HEAD method in the following router Class.
Checklist
Summary
Implementing support for the HTTP HEAD method for the /healthz endpoint enhances efficiency and reduces bandwidth usage by allowing quick retrieval of metadata about the service's health without sending the entire response body.
This aligns with HTTP standards, improves monitoring capabilities, and contributes to the scalability and reliability of the system.
Why?
I wanted to add support for the HTTP HEAD method to the /healthz endpoint because I wanted to integrate it with my monitoring service, which only supports HEAD requests. Upon further consideration, I realized the benefits it offers. Specifically, it enhances efficiency by allowing quick retrieval of metadata about the service's health without transmitting the entire response body, reducing bandwidth usage. Additionally, supporting this method aligns with HTTP standards, improves monitoring capabilities, and contributes to the scalability and reliability of the system.
How?
Adding support for the
HEAD
method in the following router Class.streamlit/lib/streamlit/web/server/routes.py
Line 125 in 98fa8c3
Additional Context
No response
The text was updated successfully, but these errors were encountered: