Skip to content

Support HTTP2 healthchecks #1001

Open
Open

Description

@ivo1116

Proposed Change

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

Related links

Activity

  1. winkingturtle-vmw commented on Feb 24, 2026

    @winkingturtle-vmw
    Contributor

    @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.

  2. ivo1116 commented on Feb 27, 2026

    @ivo1116
    ContributorAuthor

    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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions