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
On the server side this format is supported by proxies like Envoy or Improbable's grpcwebproxy.
If Vanguard supported this format it would make it easier for grpc-web users to gradually transition to Connect by allowing them to first switch their proxy to Vanguard and then incrementally update their frontend clients, without losing server side streaming support for clients that aren't yet migrated.
Hey @bhainesva thanks for reporting. I'll pick up and have a look at adding support later this week. Currently we don't support grpc-web-text across any of the connect implementations. Adding support in vanguard-go does make sense for this use case and as a first implementation. Eventually we would look at also adding in coverage in the conformance test suite.
Users of grpc-web clients that want to support streaming are currently required to use the
grpc-web-text
wire format (https://github.com/grpc/grpc-web?tab=readme-ov-file#streaming-support).On the server side this format is supported by proxies like Envoy or Improbable's grpcwebproxy.
If Vanguard supported this format it would make it easier for
grpc-web
users to gradually transition to Connect by allowing them to first switch their proxy to Vanguard and then incrementally update their frontend clients, without losing server side streaming support for clients that aren't yet migrated.Request originated in this slack thread: https://bufbuild.slack.com/archives/CRZ680FUH/p1729008888312809
The text was updated successfully, but these errors were encountered: