]> granicus.if.org Git - apache/commit
projects / apache / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: ae877f9) | patch
Immortal data should go in an immortal bucket, not a pool bucket. It would
authorCliff Woolley <jwoolley@apache.org>
Thu, 27 Sep 2001 04:01:10 +0000 (04:01 +0000)
committerCliff Woolley <jwoolley@apache.org>
Thu, 27 Sep 2001 04:01:10 +0000 (04:01 +0000)
commited3a5bc69e3a0d729e15f0c71d78091828adc1d0
tree6ec4bcf3ae4b24ed46e66e1c9368c3b36ed1199etree | snapshot
parentae877f9e70f05aceae6d78cb53be3e3c6bb6a3cdcommit | diff
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 diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.