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
We have received requests for supporting HTTP/2 healthchecks in Diego. Currently, HTTP healthchecks are performed using HTTP/1.1, but some applications require HTTP/2.
Adding support for HTTP/2 healthchecks would require introducing a new property in the app manifest to specify that the healthcheck should use HTTP/2.
Proposed Change
Introduce a new property in the application manifest, such as:
health-check-http-version: http2
When this property is set, the healthcheck should be performed using HTTP/2 instead of HTTP/1.1.
Impact
Apps handling healthchecks will need to be updated to support HTTP/2, if they specify it in the manifest
Backward compatibility is maintained—if the property is not specified, the default will remain HTTP/1.1.
Acceptance criteria
I have an app that supports a http2 healthcheck
When i specify that I want a http2 healthcheck
Then a http2 healthcheck is perforemed
Activity
winkingturtle-vmw commentedon Feb 24, 2026
@ivo1116 Is this request still relevant ? If so, can you please start a RFC in github.com/cloudfoundry/community, so that we can discuss this.
ivo1116 commentedon Feb 27, 2026
Hello, yes, this request is still relevant, but we do not have the capacity to act up on it, as it currently does not hold the highest priority for us