mod_proxy_http2: don't use ap_proxy_ssl_connection_cleanup(), there may be

data available on the backend connection before we reuse it (e.g. PING or SETTINGS change).

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@1750414 13f79535-47bb-0310-9956-ffa450edef68

diff --git a/modules/http2/mod_proxy_http2.c b/modules/http2/mod_proxy_http2.c
index 74b3dfcd8d637992e529a97e493b5f1bebcfaefe..b4186ade89cd3e5cc730d02a22b3979c8bae8b2a 100644 (file)
--- a/modules/http2/mod_proxy_http2.c
+++ b/modules/http2/mod_proxy_http2.c
@@ -520,11 +520,6 @@ run_connect:
     }
 
     ctx->p_conn->is_ssl = ctx->is_ssl;
-    if (ctx->is_ssl) {
-        /* If there is still some data on an existing ssl connection, now
-         * would be a good timne to get rid of it. */
-        ap_proxy_ssl_connection_cleanup(ctx->p_conn, ctx->rbase);
-    }
 
     /* Step One: Determine the URL to connect to (might be a proxy),
      * initialize the backend accordingly and determine the server