rolf at ohio
Jan 21, 2010, 12:57 PM
Post #3 of 5
On Jan 21, 2010, at 12:06 PM, David E. Wheeler wrote:
> It's not in the httpd.conf file unless inst/htprobe_apache2.pl fails to detect it. It'd be worth finding out why it failed to detect it on your system.
This is what I did, which seems to have caused the weirdness.
I installed the CMS, and not particularly caring about recompiling for mod_expires at some point, removed that module from line 256 (or whatever it is) of the htprobe_apache2.pl (which, btw, had no issues with apreq2 last night).
So then that line showed up in the conf. The first time it showed up wrong, something like "Loadmodule mod_expires", which obviously didn't work. The next install, it was a proper LoadModule line. But because I didn't build apache with the module, it couldn't find it. Comment out the line and apache starts up.
Now, when I rebuilt the server later, I compiled mod_expires in, but there was no .so module. The line still showed up, and of course failed. This appears to be because the htprobe file was still in a bad way from my edits, which was why it didn't detect mod_expires.
So in theory what happened to me shouldn't be an issue for anyone else. But for me the behavior is somewhat curious. Why would it put in a LoadModule line if it doesn't detect the module? And there's some LoadModule lines for apreq2 and mod_perl, too, even though they are detected and work.
I feel like the LoadModule lines weren't always at the top of httpd.conf, but I could very well be imagining things. I've always had to put them in the apache2/httpd.conf so they get detected.