You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a listener config contains an Any proto with an unknown proto type, the config
is rejected. If debug logging is turned on, though, Envoy first attempts to print the
JSON representation of the config. This caused a RELEASE_ASSERT to trigger,
crashing Envoy. This PR renames the unsafe proto-to-JSON conversion function
and replaces its usage with the safe version in the listener manager to prevent
the crash.
Signed-off-by: Alex Konradi <[email protected]>
Copy file name to clipboardexpand all lines: docs/root/version_history/current.rst
+1
Original file line number
Diff line number
Diff line change
@@ -36,6 +36,7 @@ Bug Fixes
36
36
* grpc-web: fix local reply and non-proto-encoded gRPC response handling for small response bodies. This fix can be temporarily reverted by setting `envoy.reloadable_features.grpc_web_fix_non_proto_encoded_response_handling` to false.
37
37
* http: disallowing "host:" in request_headers_to_add for behavioral consistency with rejecting :authority header. This behavior can be temporarily reverted by setting `envoy.reloadable_features.treat_host_like_authority` to false.
38
38
* http: reverting a behavioral change where upstream connect timeouts were temporarily treated differently from other connection failures. The change back to the original behavior can be temporarily reverted by setting `envoy.reloadable_features.treat_upstream_connect_timeout_as_connect_failure` to false.
39
+
* listener: prevent crashing when an unknown listener config proto is received and debug logging is enabled.
39
40
* upstream: fix handling of moving endpoints between priorities when active health checks are enabled. Previously moving to a higher numbered priority was a NOOP, and moving to a lower numbered priority caused an abort.
0 commit comments