in reply to How do you run mod_perl handlers after standard Apache handlers

AFAIK, you only have two choices. You can change one of the handlers to run at a different request stage, or you can replace mod_usertrack with Apache::Usertrack and used stacked handlers. Stacked handlers are only available for Perl handlers, so you can't do that with the original mod_usertrack.

There may be some compiling trick to adjust which one runs first. Asking on the mod_perl list is your best bet for that.

  • Comment on Re: How do you run mod_perl handlers after standard Apache handlers

Replies are listed 'Best First'.
•Re: Re: How do you run mod_perl handlers after standard Apache handlers
by merlyn (Sage) on Mar 14, 2003 at 17:58 UTC
    There may be some compiling trick to adjust which one runs first. Asking on the mod_perl list is your best bet for that.
    The running order is determined by the order in which the modules get registered, in inverse order. If you are using an Apache that uses dynamic loading, you can shuffle the order of the AddModule calls in the httpd.conf. mod_perl is normally last (or nearly last), so it runs first. If you put it ahead of mod_usertrack, it'll run after that.

    Beware... such shuffles will affect all phases, not just the one you are thinking about. Be very careful, and test on a test machine, not a production machine!

    -- Randal L. Schwartz, Perl hacker
    Be sure to read my standard disclaimer if this is a reply.

[reply]

In Section Seekers of Perl Wisdom