Figure out how Unified Header Validation (UHV) should handle characters from HPACK that it currently considers invalid
Open
area/header_validator
no stalebot
- Dominant language
- C++
- Stars
- 28.9k
- Forks
- 5.6k
- Avg merge
- 1d 22h
- Merged PRs (30d)
- 430
Description
This issue came about when doing an [QUICHE import](https://github.com/envoyproxy/envoy/pull/39802) of https://github.com/google/quiche/commit/90eab2218fc6d1d8965f3aa2199581b32f13c789.
See https://github.com/envoyproxy/envoy/pull/39802#issuecomment-2960583518 for details.
UHV needs to figure out how it should deal with HPACK encoding in a header block characters that are currently considered invalid by the Envoy validator: https://github.com/envoyproxy/envoy/blob/e52309ec7477dbc6a7e24dadc59845ed43c4d284/envoy/http/header_map.h#L35-L39
Contributor guide
Assessment
This issue has not been assessed yet.