This is definitely not the same problem. First of all the problem was fixed in 2.2.1 and the original poster reports using 2.2.2. Second, I do not see any mention of caching the response under the key http://_default_:80/ like in your case. Frankly, I do not see anything indicating the response is not cached or is cached under a key that does not correspond to the URL, in the logs posted. I would have liked to see the logs for two subsequent requests for the exact same URL though, because in this case we do not know whether the URL had been previously requested (and cached). The fact that the CACHE_SAVE filter is added means that all cache providers have declined to serve the request, i.e. no cache provider has an appropriate response. -ascs -----Original Message----- From: Nathan Seven [mailto:scosol@xxxxxxxxxx] Sent: Wednesday, May 31, 2006 12:15 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: [users@httpd] Reverse Proxy Cache not Caching in 2.2.2 I reported this earlier- it is an easy patch: http://issues.apache.org/bugzilla/show_bug.cgi?id=38017 -SS --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|