gRPC directives for pekko-http #615
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds pekko-http directives that detect grpc/grpc-web requests.
This support integration of grpc endpoints alongside other HTTP requests on the same server binding (e.g. HTTP based /healthz handlers etc.) and different handling for different protocol types (e.g. enforcing
Strict-Transport-Securityfor grpc-web requests).Java and Scala DSLs are provided.
Currently the Java DSL uses the
@InternalApiRouteHandlerfrom pekk-http - this could be copied in-tree if that's not considered maintainable.The
GrpcProtocol.detecthasn't been used, as it doesn't check the main type of the MediaType at present - alternatively that could be changed and used for this purpose as well.