Return-Path: Delivered-To: apmail-httpd-dev-archive@www.apache.org Received: (qmail 96950 invoked from network); 13 Sep 2004 20:28:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 13 Sep 2004 20:28:39 -0000 Received: (qmail 9357 invoked by uid 500); 13 Sep 2004 20:28:24 -0000 Delivered-To: apmail-httpd-dev-archive@httpd.apache.org Received: (qmail 9289 invoked by uid 500); 13 Sep 2004 20:28:23 -0000 Mailing-List: contact dev-help@httpd.apache.org; run by ezmlm Precedence: bulk Reply-To: dev@httpd.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list dev@httpd.apache.org Received: (qmail 9260 invoked by uid 99); 13 Sep 2004 20:28:23 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from [198.80.156.170] (HELO tfmagate1.tfn.com) (198.80.156.170) by apache.org (qpsmtpd/0.28) with ESMTP; Mon, 13 Sep 2004 13:28:21 -0700 Received: from ilxconn2.tfn.com (ILXCONN2.tfn.com [172.31.70.114]) by tfmagate1.tfn.com (Switch-2.2.8/Switch-2.2.8/tfn-gw-1.0) with ESMTP id i8DKSBZ08503 for ; Mon, 13 Sep 2004 16:28:11 -0400 (EDT) Received: by ILXCONN2.tfn.com with Internet Mail Service (5.5.2657.72) id ; Mon, 13 Sep 2004 16:28:10 -0400 Message-ID: <35C251B635189944B65CAB923470EA9604BA49D1@execmail.apps.ilx.com> From: "Nayak, Narayana" To: "'dev@httpd.apache.org'" Subject: Apache proxy 2.0.48 caching issues Date: Mon, 13 Sep 2004 16:23:55 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2657.72) Content-Type: text/plain; charset="iso-8859-1" X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello, We are in the migration stage from apache proxy 1.3.27 to 2.0.48. We are using this software as proxy server not web server. We have identified several issues with caching functionality in 2.0.48, however 1.3.27 is caching the content served by web servers properly. Is there a fix already available? If not, when can we expect it earliest? Is there a solution available in 1.3.x for HTTP/1.1 keep alive between proxy and web server? also the duration reporting in microseconds? Here's the list of caching issues in 2.0.48. 1) mod_cache is included in experimental. 2) After the expiry (stale content) the proxy starts sending 404 Not Found response for the cached content. 3) None of the garbage collection functionalities are implemented. 4) Cache Enable need to be listed for every possible domain, whereas in 1.3.x it was the other way. In 1.3.x we had to list only few domains under NoCache, all other contents used to get cached. We have very big list of domains to cache. I would appreciate any earlier insight on this. Thanks much, Narayana Nayak