We are on H-Sphere 3.0.0 P9.
And while H-Sphere 3.1 forward (Parallels maintains several product lines like mySQL, Apache, etc. -- most of which is considered stable and alive) does support the option to pick on a server-by-server basis whether to be on Apache 1 or Apache 2, we've not yet seen enough incentives to be on Apache 2.
While mod_security 2 is one incentive, it is not large enough to have us leave an extremely stable, supported by the Apache community (that is to state, not declared EOL), Apache 1 along with the stability we have with H-Sphere 3.0.0 P9 (almost all of the new versions - multi-branch like mySQL, Apache, etc.) have stability issues.
What I don't understand is that since Apache 1.3.41 has not been declared EOL, and Apache 1 is still very popular, why Breach doesn't support both versions of Apache. But that's just my own lack of understanding.
Peter M. Abraham
Support and Customer Care Department
Dynamic Net, Inc.
Helping companies do business on the Net
Denver, PA 17517
Toll Free Voice: 1-888-887-6727
> -----Original Message-----
> From: Brian Rectanus [mailto:Brian.Rectanus@...]
> Sent: Monday, January 04, 2010 5:38 PM
> To: support.team@...
> Cc: mod-security-users@...
> Subject: Re: [mod-security-users] Does mod_security 1.9.5 work with 64-bit unix?
> Peter M. Abraham wrote:
> > Greetings:
> > We and many of our colleagues use a hosting automation system where Apache
> > 1.3 (Apache, like mySQL maintains several production lines) is still the
> > flavor and will be for a number of years to come.
> > Are there any adjustments that need to be made to mod_security.c under Mod
> > Security 1.9.5 for it to compile under CentOS 5.4 64-bit when using Apache
> > 1?
> What automation system are you using that is not at least Apache 2.0