We are finally planning to "do the right thing" and have a light weight and
heavy weight server. Our problem is that our (immediate) users set up
the protections for each directory with .htaccess files - and they use
PerlAuthzHandler and PerlAuthenHandlers - so to decide if a file can be
If you are using shared repositories for the front-end and heavy
server you can modify the filename used for .htaccess in the apache
config file. (See the AccessFileName entry)
So, you could put the config for the heavy server in .htaccess_heavy
and the front-end config in .htaccess.
On Wed,
So, you could put the config for the heavy server in .htaccess_heavy
and the front-end config in .htaccess.
Sorry - didn't make myself clear. The protection on the files are the same -
just too complex for the front-end to understand (since use modperl).
So if there is any authentication
Or if you want to share some directives but not others, you can use
IfModule mod_perl.c or IfDefined SomeSymbol sections to block one
server from reading those portions of the config files.
[EMAIL PROTECTED] (Paul Lindner) wrote:
If you are using shared repositories for the front-end and heavy
As long as you can garantee that the URI of the resource is not accessible
multiple ways you could use a Location/ directive on the relative path.
Trouble with this is my problem arises out of a (deliberate) lack of central
control. That is, I have thousands of directories, and the web
