From e349fb6139e4b7a59a9a359be0ea45dd61e589c5 Mon Sep 17 00:00:00 2001 From: Piotr Sikora Date: Mon, 5 Aug 2019 15:27:47 -0700 Subject: [PATCH] release: bump to 1.11.1. (#21) Signed-off-by: Piotr Sikora --- VERSION | 2 +- docs/root/intro/version_history.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/VERSION b/VERSION index 1cac385c6cb8..720c7384c619 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -1.11.0 +1.11.1 diff --git a/docs/root/intro/version_history.rst b/docs/root/intro/version_history.rst index 287627a6af85..a27b4118bba0 100644 --- a/docs/root/intro/version_history.rst +++ b/docs/root/intro/version_history.rst @@ -1,8 +1,8 @@ Version history --------------- -1.11.1 (Pending) -================ +1.11.1 (August 13, 2019) +======================== * http: added mitigation of client initiated attacks that result in flooding of the downstream HTTP/2 connections. Those attacks can be logged at the "warning" level when the runtime feature `http.connection_manager.log_flood_exception` is enabled. The runtime setting defaults to disabled to avoid log spam when under attack. * http: added :ref:`inbound_empty_frames_flood ` counter stat to the HTTP/2 codec stats, for tracking number of connections terminated for exceeding the limit on consecutive inbound frames with an empty payload and no end stream flag. The limit is configured by setting the :ref:`max_consecutive_inbound_frames_with_empty_payload config setting `. Runtime feature `envoy.reloadable_features.http2_protocol_options.max_consecutive_inbound_frames_with_empty_payload` overrides :ref:`max_consecutive_inbound_frames_with_empty_payload setting `. Large override value (i.e. 2147483647) effectively disables mitigation of inbound frames with empty payload.