Great to hear you got it running, unfortunately I only have about a two week head start on you with regard to the apache front, so I am sure lots of things will get neater as we go along.<br><br><div class="gmail_quote">2009/3/16 Alex Wulms <span dir="ltr"><<a href="mailto:alex.wulms@scarlet.be">alex.wulms@scarlet.be</a>></span><br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi Toby,<br>
<br>
I managed to get it working on my PC under suse 11.1 with apache 2.2.10.<br>
<br>
When I configured a dedicated debug log per virtual server, I noticed that the<br>
crccache_client and crccache_server modules were both invoked in both virtual<br>
servers. Judging from the error log you sent me, that is also the case on<br>
your server.<br>
<br>
I have made following changes to fix the situation:<br>
<br>
1) Move the 'CacheEnable crccache_client' directive (for the 'default' virtual<br>
server) inside the <VirtualHost> tag. Apparently it is applied globally as<br>
long as it is outside the <VirtualHost> tag, regardless of the config file in<br>
which it appears.<br>
</blockquote><div>Seems like a sensible change. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
2) Introduce a new directive 'CRCCacheServer on'.<br>
This directive is checked by mod_crccache_server in the<br>
crccache_server_header_parser_handler.<br>
It is specified in the <VirtualHost> tag of the upstream_proxy of the virtual<br>
server.<br>
Apparently modules get loaded globally and functions like<br>
the ..._header_parser_handler get invoked for each virtual server, so they<br>
must check themselves if they should be enabled or disabled in a given<br>
virtual server. I found this through google, which pointed me to a forum<br>
where somebody else had faced a similar problem.<br>
</blockquote><div>Makes sense <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I also realize why I only found cached files<br>
under /var/cache/apache2/mod_crccache_server and not under ..._client.<br>
It is because the crccache_client.conf and crccache_server.conf file both use<br>
the parameter CacheRoot to store the cache directory. These parameters are<br>
apparently also global. The fact that they are in two different config files<br>
does not automagically store them in a module specific namespace. So I have<br>
renamed the parameters to differentiate between the client and the server<br>
module.<br>
</blockquote><div>Actually only the client end should need the CacheRoot at all, the server side doesnt need caching at all. You could configure a standard apache cache if you wanted, but it probably wont gain much. <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
I have also noticed that, although the server module reads these parameters,<br>
they actually don't get used by the current code. Are they there due to<br>
copy&paste reasons or are they already there for future enhancements, in<br>
order to cache stuff temporary on the server side?<br>
</blockquote><div>Just copy and paste I guess, I think I left them there so I can something to base other parameters on if we need them server side. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
I have pushed my changes to the repository. Please review them. I'm still new<br>
to Apache development so I might have misinterpreted some things.<br>
<div class="im"><br>
Thanks and kind regards,<br>
Alex<br>
<br></div></blockquote></div><br clear="all"><br>-- <br>This email is intended for the addressee only and may contain privileged and/or confidential information<br>