For my money, apache 1.3 is the only apache. It's extremely stable and most of the security issues have been patched. Solid, solid code and a breeze to compile.
Agreed. I have been working on upgrading for quite a while but there is one issue I haven't figured out yet:
lingerd in apache 2.2 _with_ mod_php in pref_fork (as many linux source libs used in PHP not thread-safe).
As soon as the question comes up about linger_close people say "it doesn't matter in cuz its so multi-thredded coolz" but that does no good in a PHP app server model.
Anyone know if lingerd is still needed in 2.2-pre-fork mode? Cuz I know the module has not been updated for 2 family..
1.3 (Score:3, Interesting)
For my money, apache 1.3 is the only apache. It's extremely stable and most of the security issues have been patched. Solid, solid code and a breeze to compile.
But remember: I am a grumpy old man.
Re: (Score:1)
I am a grumpy old man.
I don't like new software. They haven't made anything good since about 1990.
Re: (Score:2)
Agreed. I have been working on upgrading for quite a while but there is one issue I haven't figured out yet:
lingerd in apache 2.2 _with_ mod_php in pref_fork (as many linux source libs used in PHP not thread-safe).
As soon as the question comes up about linger_close people say "it doesn't matter in cuz its so multi-thredded coolz" but that does no good in a PHP app server model.
Anyone know if lingerd is still needed in 2.2-pre-fork mode? Cuz I know the module has not been updated for 2 family..
Re: (Score:1)
I would have been in the same boat if I didn't want to use SNI with Apache 2.
Or does Apache 1.3 actually support SNI now?