httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Murcko <ch...@topsail.org>
Subject Re: APACI and module calling order
Date Thu, 11 Jun 1998 01:12:26 GMT
Ralf S. Engelschall wrote:
> 
> In article <357E6A15.D7893524@topsail.org> you wrote:
> 
> > How do I control module calling order in the build using APACI config?
> > There's no mention of it in the docs, though I can guess implicit
> > ordering of some sort from command line order.
> 
> > Two examples:
> 
> > I want to insert mod_proxy right after logging, for an outbound proxy
> > for a site.
> 
> > I want to insert SSL followed by mod_proxy as early as possible in the
> > processing chain, for a machine that will receive SSL encrypted
> > requests, and ProxyPass 'em somewhere else, possibly reencrypting them
> > on the way.
> 
> Hmmm... the situation that one wants to _control_ the order itself is not
> supported. You can add enable/disable/make-shared modules in any order on the
> "configure" command line. Because "configure" doesn't create a
> src/Configuration.apaci from scratch. Instead it reads src/Configuration.tmpl
> and _substitutes_ the content based on the users enable/disable/make-shared
> options. No restructuring of the file is done. And IMHO it is good this way or
> the user would be totally confused when the order of options is relevant.
> 
> But you can do a trick: Use "configure ... --enable-shared=max" and then APACI
> creates you a complete "ClearModuleList ... AddModule AddModule" in httpd.conf
> which you then can use to order the modules _under runtime_. This is IMHO not
> only the currently supported approach. It is also a good approach.
> 
Thanks. Fortunately, I can use DSO for the platforms I'm considering
this goofy stuff on.
-- 
chuck
Chuck Murcko            The Topsail Group             West Chester PA
USA
chuck@topsail.org

Mime
View raw message