>
> To do access control for static files while still using your mod_perl
> auth handler, take a look at mod_auth_tkt or perlbal.
>
Thanks!
On Mon, Mar 29, 2010 at 4:24 AM, Dan Axtell wrote:
> server on the back end. It seems like a lot of overhead to have mod_perl on
> the front end purely for authentication; I might as well keep the monolithic
> configuration I have now. Thanks for the input, though, it helps clarify
> things.
It
On Sun, Mar 28, 2010 at 3:41 PM, Dan Axtell wrote:
> What I don't understand is what to do about static directories that want to
> use the handlers via Directory directive, or via a local .htdocs file. Does
> any such directory need to be forwarded to the dynamic server in order to then
> call th
>
> It would be more logical to do the authentication on the front-end
> server. Then, if the back-end server needs the result of the
> authentication, you could add an appropriate HTTP header (with the
> user-id and maybe more stuff) to the request, before proxying it to the
> back-end.
> The idea
Dan Axtell wrote:
Hi,
I wrote some mod_perl handlers for authentication and authorization, basically
to set cookies and check user roles. I use them for both static and dynamic
content from Perl scripts.
I'm looking into splitting Apache into two servers, one optimized for static
content a
