From ed3a5bc69e3a0d729e15f0c71d78091828adc1d0 Mon Sep 17 00:00:00 2001 From: Cliff Woolley Date: Thu, 27 Sep 2001 04:01:10 +0000 Subject: [PATCH] Immortal data should go in an immortal bucket, not a pool bucket. It would still work in a pool bucket, but only by coincidence. At the very least, a pool bucket is way more overhead than this poor unsuspecting little CRLF needs to get by. git-svn-id: https://svn.apache.org/repos/asf/httpd/httpd/trunk@91160 13f79535-47bb-0310-9956-ffa450edef68 --- modules/proxy/proxy_http.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/modules/proxy/proxy_http.c b/modules/proxy/proxy_http.c index 6540933cc1..4ebff5be95 100644 --- a/modules/proxy/proxy_http.c +++ b/modules/proxy/proxy_http.c @@ -588,7 +588,7 @@ apr_status_t ap_proxy_http_request(apr_pool_t *p, request_rec *r, } /* add empty line at the end of the headers */ - e = apr_bucket_pool_create(CRLF, strlen(CRLF), p); + e = apr_bucket_immortal_create(CRLF, sizeof(CRLF)-1); APR_BRIGADE_INSERT_TAIL(bb, e); e = apr_bucket_flush_create(); APR_BRIGADE_INSERT_TAIL(bb, e); -- 2.40.0