Question: Support for http2/3 health checks?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15
- Forks
- 13
- Avg merge
- 4d 7h
- Merged PRs (30d)
- 2
Description
Expected Behavior
Does NetCHASM support http2 (or later) health checks?
It's unclear from my scanning of the documentation whether NetCHASM supports making health checks to servers which support only http2 (i.e. no http/1.1 support).
Current Behavior
Change would be to add http2 support (if it does not exist).
Context
Such support would be useful for checking servers running gRPC services which are http2 based, but do not support http/1.1. We often have a situation now running Java gRPC services where a health check comes in for, say, GET /status.html HTTP/1.1 on the same port as the Java gRPC service. In Java gRPC, this results in an error and a long stack backtrace (see https://github.com/grpc/grpc-java/issues/7692).
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by reviewing the documentation and locating the existing health-check implementation to determine whether it supports HTTP/2-only servers; define the required behavior for gRPC health checks and identify tests needed to demonstrate support.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp, grpc
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100