Slashdot Mirror


Is Apache 2.x Ready for General Use?

Above asks: "In this article we see apache 2.0.45 has been released. Well, I plan on rebuilding my webserver soon, which means installing the "latest" version. However, I'm still on the 1.x train, which is still going strong. As someone who hasn't used 2.x, and hasn't followed the development is it ready for the masses or should I stick with 1.x and be happy? Are mod_perl and ssl (my two requirements) stable? What about all the other things (php et all)? I don't do anything fancy with my web sites, but having them "just work" and not having to upgrade every other day are both strong concerns. What are your experiences?"

1 of 41 comments (clear)

  1. Apache 2 is ready, but why bother? by MS_is_the_best · · Score: 5, Interesting

    Yes, Apache 2 is stable and ready for some time. No doubt about that, it runs on lots of productions sites (check netcraft.com).

    Also mod_php, ssl and mod_php are working fine. (although shorter then Apache 2 itself). This is partly because Apache 2 wants thread-safety and some modules (actually not sure about Perl) aren't.

    Is see no particular reason not to install Apache 2, but also no reason to do. Redhat is used a lot by internet providers and ships with 2.0 default since 8.0. The 1.3 branch is still maintained and seems faster on Unix-based systems (with fork). On Windows Apache 2 wins, due to the use of threads.

    This is a bit standard answer (everyone knows this things, easy to find out), so I want to ask this: How long will all products (mod_*) still work just as good under Apache 1.3.x as under 2.0.x and will 3rd party providers drop support for 1.3 soon? (thus 'forcing' us to upgrade)?