Fix problem where a 304 response was not generating an EOS bucket.

ap_finalize_request_protocol()'s sole purpose in Apache 2.0 is to
send the EOS bucket. Probably need to reimplement ap_send_error_response()
to be consistent with ap_finalize...'s new mission.

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

diff --git a/modules/http/http_protocol.c b/modules/http/http_protocol.c
index 091586b36881e9b14539f0c5cd9354ba0e90cf84..2ad8ea7e73ebb131acc74ec79af45c967865e069 100644 (file)
--- a/modules/http/http_protocol.c
+++ b/modules/http/http_protocol.c
@@ -2267,7 +2267,7 @@ AP_CORE_DECLARE_NONSTD(apr_status_t) ap_http_header_filter(ap_filter_t *f, ap_bu
         apr_table_unset(r->headers_out, "Content-Length");
         /* Disable the buffer filter because it may be masking bugs in the 
          * bucket brigade code  */
-        ap_add_output_filter("COALESCE", NULL, r, r->connection);
+//        ap_add_output_filter("COALESCE", NULL, r, r->connection);
         ap_add_output_filter("CHUNK", NULL, r, r->connection);
     }
 
@@ -3157,7 +3157,7 @@ AP_DECLARE(void) ap_send_error_response(request_rec *r, int recursive_error)
                     NULL);
 
         terminate_header(r);
-
+        ap_finalize_request_protocol(r);
         return;
     }