config: extending usage of EnvoyMobileHttpConnectionManager (#17407)
#17110 the EnvoyMobileHttpConnectionManager but it turns out it's instantiated either as a standard network filter (needs a name) or as an API listener (which only accepted HttpConnectionManager) Fixing both issues. Risk Level: low Testing: unit tests Docs Changes: n/a Release Notes: n/a Part of envoyproxy/envoy-mobile#1540 Signed-off-by: Alyssa Wilk <alyssar@chromium.org> Mirrored from https://github.com/envoyproxy/envoy @ 463eda2f3895fbb24c1fcd085a15d00d12a94079pull/624/head
parent
ca81738dc4
commit
b73e171a20
4 changed files with 4 additions and 0 deletions
Loading…
Reference in new issue