From ca1c99310357405592fbd24342166db491cae6f6 Mon Sep 17 00:00:00 2001
From: Jim Jagielski <jim@apache.org>
Date: Sun, 19 Apr 2015 18:18:10 +0000
Subject: [PATCH] backport question/vote

git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/branches/2.4.x@1674663 13f79535-47bb-0310-9956-ffa450edef68
---
 STATUS | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/STATUS b/STATUS
index 6c82a15351..51900f1f94 100644
--- a/STATUS
+++ b/STATUS
@@ -224,6 +224,12 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
                   http://svn.apache.org/r1656359 (CHANGES entry)
      2.4.x patch: trunk works (modulo CHANGES, docs/log-message-tags)
      +1: ylavic
+     -0: jim:  This seems to be a hit to normal performance, to handle an
+               error and/or non-normal condition. The pre-fetch is
+               expensive, and is always done, even before we know that
+               the backend is available to rec' it. I understand the
+               error described, but is the fix actually worth it (plus
+               it seems to allow for a DDoS vector).
 
   *) http: Make ap_die() robust against any HTTP error code and not modify
      response status (finally logged) when nothing is to be done. PR 56035.
-- 
2.50.1