Avoid using HeaderMapImpl for gRPC metadata
Open
area/security
bug
help wanted
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 430
Description
Today, we use `HeaderMapImpl` for gRPC metadata, e.g. https://github.com/envoyproxy/envoy/blob/3dd84d3b41b6be378ccb71e81c0063a84bb956e3/include/envoy/grpc/async_client.h#L70. This is not safe, since in general, this metadata may contain binary and `HeaderMapImpl` can't contain NUL.
We should switch to using a simple map or the like to model these values, treating them as metadata rather than headers.
Contributor guide
Assessment
This issue has not been assessed yet.