Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

V2: Require HTTP/2 for the gRPC transport #1279

Merged
merged 2 commits into from
Oct 17, 2024

Conversation

timostamm
Copy link
Member

@timostamm timostamm commented Oct 15, 2024

gRPC implementations typically require HTTP/2, but the protocol itself does not. connect-es can run gRPC over HTTP 1.1, but that requires support for HTTP trailers end to end. This can be difficult to achieve and guarantee, and most other gRPC implementations do not support it, so we are disabling support for gRPC over HTTP 1.1 in version 2.

Closes #1258.

@timostamm timostamm changed the title Require HTTP/2 for the gRPC transport V2: Require HTTP/2 for the gRPC transport Oct 16, 2024
@timostamm timostamm marked this pull request as ready for review October 16, 2024 12:32
packages/connect-node/src/node-readme.spec.ts Show resolved Hide resolved
Comment on lines +26 to +27
// @ts-expect-error TS2353: Object literal may only specify known properties, and httpVersion does not exist in type GrpcTransportOptions
httpVersion: "2",
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

httpVersion cannot be specified for createGrpcTransport anymore. It always uses HTTP/2.

@timostamm timostamm merged commit f6c9fac into v2 Oct 17, 2024
47 checks passed
@timostamm timostamm deleted the tstamm/v2/Require-HTTP/2-for-the-gRPC-transport branch October 17, 2024 10:27
@timostamm timostamm mentioned this pull request Oct 18, 2024
@srikrsna-buf srikrsna-buf mentioned this pull request Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants