Avoid using HeaderMapImpl for gRPC metadata
Aperta
area/security
bug
help wanted
- Lingua principale
- C++
- Stelle
- 28.9k
- Fork
- 5.6k
- Merge medio
- 1g 22h
- PR unite (30g)
- 430
Descrizione
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.
Guida per i contributori
Apri la guida per i contributori
Valutazione
Questa issue non è ancora stata valutata.