From: Eric Covener <covener@apache.org>
Date: Sat, 27 Aug 2016 21:08:08 +0000 (+0000)
Subject: emphasize that the flush in 2.2.x check_pipeline_flush() is actually
X-Git-Tag: 2.2.32~85
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7f6819b34545a3aa562d188a597080e6657bccff;p=thirdparty%2Fapache%2Fhttpd.git

emphasize that the flush in 2.2.x check_pipeline_flush() is actually
unconditional



git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.2.x@1758071 13f79535-47bb-0310-9956-ffa450edef68
---

diff --git a/modules/http/http_request.c b/modules/http/http_request.c
index fc8d43309d5..75d9b79365b 100644
--- a/modules/http/http_request.c
+++ b/modules/http/http_request.c
@@ -255,6 +255,10 @@ static void check_pipeline_flush(request_rec *r)
         }
     }
 
+    /* The flush below became unconditional way back in r105919. Later
+     * branches have very different handling in this area anyway (EOR bucket).
+     */
+
         e = apr_bucket_flush_create(c->bucket_alloc);
 
         /* We just send directly to the connection based filters.  At