There is currently no support for encoding grpc trailers in HTTP responses using the GRPC HTTP1 Reverse Bridge

In the [GRPC HTTP1 Reverse Bridge](https://www.envoyproxy.io/docs/envoy/latest/configuration/http/http_filters/grpc_http1_reverse_bridge_filter), there is currently no support to encode custom trailers in the GrpcWeb responses, that will be translated back to GRPC Response trailers. Currently, it seems that just the grpc-status is auto-inferred using the HTTP response code.

Is this something that can be added?

Here is the code for the grpc http1 reverse bridge:
https://github.com/envoyproxy/envoy/tree/5248a4fb7d4c2a3d1fa151f944d3a63f6b7a06cf/source/extensions/filters/http/grpc_http1_reverse_bridge