Sebastian Rahtz wrote:
So can anyone give some hints as to what I can expect to "just work"
and what else may involve pain?
.... but it turns out AxKit 2 is nothing to do with Apache at all (do I
understand right?),
so anything related to apache will have to be rewritten.
some care to describe the mixed Apache2/AxKit2 scenario?
Yes - there's no use of Apache in AxKit2 (although it's still an ASF
project).
Here's my setup for home.sergeant.org:
<VirtualHost 62.173.71.110>
ServerName home.sergeant.org
ProxyRequests Off
ProxyPass / http://home.sergeant.org:8001/
ProxyPreserveHost On
</VirtualHost>
(along with the regular minimal apache2 config - ask me offline if you
want the whole thing).
Now admittedly that doesn't run mod_perl on the frontend, but there is
nothing stopping you doing so, so that you can run Apache::* modules for
auth. Apache::Session is a bit different - as that's integrated into
your app. Instead I recommend using the cachecache plugin for sessions.
Just generate a unique cookie (see the webmail code for an example that
works perfectly) and store values in the cache under that key.
Matt.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]