Skip to content

Setting gRPC status in http response #148

Closed
@wagenet

Description

@wagenet

Is this possible? It looks like the underlying interface may support it, but it doesn’t seem to be public.

Activity

juanmolle

juanmolle commented on Oct 18, 2023

@juanmolle

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

juanmolle commented on Oct 24, 2023

@juanmolle

@PiotrSikora let us know what you think about this please

added a commit that references this issue on Jul 18, 2024
04f267a
added a commit that references this issue on Jul 19, 2024
2500068
PiotrSikora

PiotrSikora commented on Jul 19, 2024

@PiotrSikora
Member

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.

added a commit that references this issue on Jul 21, 2024
5c570fe
added a commit that references this issue on Oct 23, 2024
b716999
added a commit that references this issue on Nov 27, 2024
f6b2395
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

      Participants

      @wagenet@PiotrSikora@juanmolle

      Issue actions

        Setting gRPC status in http response · Issue #148 · proxy-wasm/proxy-wasm-rust-sdk