Skip to content

[💡 FEATURE REQUEST]: Propagate arbitrary headers to the erroneous response #2006

Description

@rauanmayemir

Plugin

GRPC

I have an idea!

Currently, grpc plugin accepts error field as part of response headers which is a base64-encoded google.rpc.Status payload with the error code, message, details, etc.

However, it's not possible to pass server response headers (like X-Correlation-Id, X-Request-Id, etc) together with the error.

A suggestion would be to allow sending metadata headers from workers like so:

{
  "error": "base64_encoded_proto",
  "headers": {"header_key_1": "header_value_1", "header_key_2": "header_value_2"}
}

Metadata

Metadata

Assignees

Labels

C-feature-requestCategory: feature requested, but need to be discussed

Type

No type

Fields

No fields configured for issues without a type.

Projects

Status
✅ Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions