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
I'd suggest disabling trailer validation in this case.
The text was updated successfully, but these errors were encountered:
dalechyn
changed the title
Using HTTP/1.1 via grpc transport is not possible,
Using HTTP/1.1 via grpc transport is not possible, protocol error: missing statusJan 3, 2025
gRPC requires HTTP trailers. For example, a streaming call could return a message, but then fail to return the next one. This error is encoded in HTTP trailers. When the trailers are missing, you'd never know that the call failed.
Because of this pitfall, we've disabled support for HTTP 1.1 with gRPC in #1279.
If you need HTTP 1.1, we recommend using the Connect protocol, or gRPC-Web. Both encode the status for streaming calls in the body, and do not need HTTP trailers.
connect-es/packages/connect/src/protocol-grpc/transport.ts
Line 146 in a8f2f22
This LOC checks for trailers, but when HTTP/1.1 is used no trailers are present, which always leads to
protocol error: missing status
error.connect-es/packages/connect-node/src/node-universal-client.ts
Line 148 in a8f2f22
I'd suggest disabling trailer validation in this case.
The text was updated successfully, but these errors were encountered: