proxy_protocol: evaluate format_string in upstream added_tlvs (#47369)
Description
This PR fixes the upstream proxy protocol transport socket to honor
format_stringinadded_tlvs. Before this change only the static value field was read, soformat_stringentries were ignored.These entries are now compiled at config load and evaluated per connection against the upstream connection stream info, then emitted in the proxy protocol v2 header. This reuses the same mechanism as the
tcp_proxyfilter. An entry that sets both value andformat_string, or neither, is now rejected at config load.Fix https://github.com/envoyproxy/envoy/issues/45130
Commit Message: proxy_protocol: evaluate format_string in upstream added_tlvs Risk Level: Low Testing: Added Tests Docs Changes: Added Release Notes: Added
Signed-off-by: Rohit Agrawal rohit.agrawal@databricks.com
Mirrored from https://github.com/envoyproxy/envoy @ cd73cf5553aa8e03c9d9ce46ca98fcb5b6a45ac9
版权所有:中国计算机学会技术支持:开源发展技术委员会
京ICP备13000930号-9
京公网安备 11010802047560号
Data plane API
This tree hosts the configuration and APIs that drive Envoy. The APIs are also in some cases used by other proxy solutions that aim to interoperate with management systems and configuration generators that are built against this standard. Thus, we consider these a set of universal data plane APIs. See this blog post for more information on the universal data plane concept.
Repository structure
The API tree can be found at two locations:
Further API reading