By does not work, I just mean nothing within it is processed. I
understand that it is because the modules were loaded after the vhost
in this case, and I've corrected that. I just found it odd that even
though the modules were loaded after the vhosts, the module directives
worked when I removed the IfModule block. Sorry I used the wrong
list. I'll subscribe to the user list to see if they have any
thoughts on this.
-William Leonard
Quoting André Malo <[email protected]>:
Also this belongs to the user list...
nd
On Thursday 12 April 2012 10:44:04 Igor Galić wrote:
----- Original Message -----
> I wonder if you would consider this a bug. Here is the situation.
>
> I had a config file in conf.d which loaded some modules.
> Alphabetically, it came after the loading of the vhost files. The
> IfModule blocks would not work. In this same order, if I don't use
"would not work" << what, exactly, does that mean?
Didn't parse/execute/was ignored?
What did it look like?
What, exactly, did the error log say?
> IfModule, the directives still work fine. I don't know if this is
> expected behavior, but I would think either the IfModule should work
> or if the reason the IfModule doesn't work is because the modules
> weren't loaded yet, I should get an error and the directives
> shouldn't work when I don't use the IfModule. Makes sense?
only with more context;)
> -William Leonard
i
----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
