mod_cache stable is very nice. Unfortunately, it doesn't play nice with reverse proxies. Which is too bad for me, since that is, of course, the first thing I tried to make it do. The patch to fix this has made it to the 2.2 branch upstream. This issue should be resolved in 2.2.1. I have no knowledge whatsoever of when 2.2.1 is coming out, but if you're going to push another 2.2.0, I'd suggest patching for this. ebuild /usr/portage/net-www/apache/apache-2.2.0-r1.ebuild unpack cd /var/tmp/portage/apache-2.2.0-r1/work A=http://svn.apache.org/repos/asf svn log -v -r374931 $A > cache-reverse-proxies.upstream.patch svn diff -r374930:374931 $A/httpd/httpd/branches/2.2.x/modules \ >> cache-reverse-proxies.upstream.patch patch -d httpd-2.2.0/modules -p0 < cache-reverse-proxies.upstream.patch ebuild /usr/portage/net-www/apache/apache-2.2.0-r1.ebuild merge And now it works.
Created attachment 81088 [details, diff] upstream patch
Upstream bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=38017 Fixed in 2.2.x branch, will be in next release.
Update: apache-2.2.0-r2 is out without this patch. As Paul noted, this fix has already been backported to the 2.2.x branch. As should have been mentioned originally and as stated in the upstream bug report, this is a regression against apache-2.0.
Yes, this is a regression from 2.0. However, 2.2 in gentoo is still experimental. We do not need a play by play of every -r bump of the masked package. We will get to it when we get to it.
Thanks for the comment and your efforts. I promise not to touch this bug again :).
Apache 2.2.2 is now in the tree, which includes this fix.
