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
Note that Envoy doesn't support sending gRPC messages using sendLocalReply() calls, and it automatically changes HTTP responses to gRPC errors when talking with gRPC clients, so this is limited to emitting gRPC error responses, and not for producing valid gRPC responses.
Activity
juanmolle commentedon Oct 18, 2023
Do we need to expose? maybe instead of return -1 https://github.com/proxy-wasm/proxy-wasm-rust-sdk/blob/master/src/hostcalls.rs#L721 we can map http code to the closest grpc code
juanmolle commentedon Oct 24, 2023
@PiotrSikora let us know what you think about this please
Add support for sending error responses with gRPC status codes.
Add support for sending error responses with gRPC status codes.
PiotrSikora commentedon Jul 19, 2024
This should be fixed in #248.
Note that Envoy doesn't support sending gRPC messages using
sendLocalReply()
calls, and it automatically changes HTTP responses to gRPC errors when talking with gRPC clients, so this is limited to emitting gRPC error responses, and not for producing valid gRPC responses.Add support for sending error responses with gRPC status codes. (prox…
Add support for sending error responses with gRPC status codes. (prox…
Add support for sending error responses with gRPC status codes. (prox…