In Apache 2.0 configurations you have no way of defining the order in which you wish the processing to take place. The order is more or less determined by the modules themselves, specifically by the way they register their hooks. A hook can be registered as FIRST, MIDDLE or LAST to roughly specify when it is supposed to be executed. The API also provides the possibility to specify modules that have to run before or after, if necessary. An I tell you: as an Apache administrator it really is a relief not to have to worry about the order in which the modules are executed. That's one less thing that can go wrong, therefore one less thing to consider when shit hits the fan. -ascs -----Original Message----- From: Jérôme Tytgat [mailto:jerome.tytgat@xxxxxxxxxxx] Sent: Monday, August 29, 2005 10:55 AM To: users@xxxxxxxxxxxxxxxx Subject: Re: [users@httpd] Re: Problems with proxying remote URLs > If memory serves me right, the modules added last are the ones executed first. > You want mod_proxy to be executed after mod_rewrite so mod_rewrite must be loaded after mod_proxy. Interesting point, I was facing that kind of problem when I wanted to do rewrite rules plus proxypass. What about Apache2 ? How do you define the order when you use mods-enabled directory ? By changing the name order ? (mod_proxy come first in directory listing) Jerome. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|