From: Yann Ylavic <ylavic@apache.org>
Date: Thu, 24 Sep 2015 11:37:09 +0000 (+0000)
Subject: Is it the right fix?
X-Git-Tag: 2.2.32~178
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d1abcd5f57a2e83b9388e5da976261c04c2346b6;p=thirdparty%2Fapache%2Fhttpd.git

Is it the right fix?

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

diff --git a/STATUS b/STATUS
index ff75a55e367..e5c2044f2c6 100644
--- a/STATUS
+++ b/STATUS
@@ -158,6 +158,12 @@ PATCHES PROPOSED TO BACKPORT FROM TRUNK:
      ylavic: don't we know from the very beginning of store_body() if
              r->connection->aborted, so to fail there?
      rpluem: Agreed. I guess we can move this up to line 733 before the loop.
+     ylavic: Or even at the beginning if we want to avoid file caching too.
+             But finally I wonder why we would not cache the response provided
+             it is complete. Shouldn't incomplete response be detected with
+             error buckets instead? ISTM that EOS with no error bucket *is*
+             a complete response that could be cached even if the current
+             client won't receive it completely.
 
   *) mod_proxy: don't recyle backend announced "Connection: close" connections
      to avoid reusing it should the close be effective after some new request