I agree with Chris. For us it is a lost functionality now. It was working fine in 1.3.x proxy. Also I would like to highlight, the cache enabling functionality is reversed in 2.0. In other words, we have to list all possible domains to enable it with disk cache. Default is cache disabled in 2.0 whereas in 1.3.x, we had a very few list for NoCache and by default 1.3.x used to cache all other responses. 2.0.51 is not yet released as stable version, which raises concern on using it in production environment. What is the timeframe for 2.0.51? Where do I get it for a try?
Thanks much, Narayana Nayak -----Original Message----- From: chris [mailto:[EMAIL PROTECTED] Sent: Monday, September 13, 2004 12:01 PM To: [EMAIL PROTECTED] Subject: Re: Apache proxy 2.0.48 caching issue Thank you for the response Graham, I will direct future mod_cache queries to that list. It's certainly possible I was in the wrong spot. I was a bit lost out there. Here is the area of CVS I have been digging around for info in: http://cvs.apache.org/viewcvs.cgi/httpd-2.0/modules/cache/ If there is somewhere else where I need to be looking to try out the latest fixes, I would be grateful if you could direct me there. I'm very anxious to get caching back on. It really reduces the number of inbound connections to the real servers from my reverse proxies. Thanks much, chris rhodes On Mon, 2004-09-13 at 10:45, Graham Leggett wrote: > chris wrote: > > > I see this as well in 2.0.50. I took a look in cvs and did not see much > > new with mod_cache in around 7 months. I'm guessing this is a problem > > with it and not really mod_proxy so this will likely fall on deaf ears > > here on this list. > > mod_cache is entirely separate from mod_proxy - queries should be > directed to the dev@httpd.apache.org list instead. > > As to mod_cache, there have been a whole lot of fixes which have gone > into v2.1.0, and to my knowledge into v2.0.51 - are you looking at the > most recent CVS? > > Regards, > Graham > --
