If this is with ActivePerl 8xx, though, then it may be that there's an incompatibility between modules compiled against Apache 2.0.44 (which the mod_perl ppm package on our site was compiled against) and Apache 2.0.45. The Apache group says that, starting with 2.0.42, they're working at maintaining configuration and module interface compatibility, so in principle upgrading from 2.0.44 to 2.0.45 shouldn't be a problem. But with a combination of Win32 and the relative complexity of mod_perl 2, this compatibility may not have survived .... I've tried compiling the current cvs mod_perl 2 sources against Apache 2.0.45, but have run into a problem (unrelated to the 2.0.45 upgrade) that hasn't yet been resolved. Given the security fixes for Win32 present in 2.0.45, if you feel uneasy about reverting to 2.0.44, I could make available a mod_perl 2 package based on not-so-current cvs sources compiled against 2.0.45 until the problem in the current cvs version is fixed.
Just had another thought... maybe you should indeed recompile mod_perl-2 with the older CVS sources, so I can try it out on Apache 2.0.45, and we can be 100% sure that this is the problem...
Maybe the problem really is that the old binaries aren't compatible with the new Apache, but at the moment we just don't know. Trying it out would help.
Of course it's not necessary if it means too much effort... it would be interesting though to see if the recompile really does solve the problem.
Thank You,
Sebastian.--
If You're European, do something for YOUR civil rights: http://www.stop1984.com
Stop software patents in the EU! http://swpat.ffii.org
