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?"

2 of 41 comments (clear)

  1. If it Ain't Broke... by Michael's+a+Jerk! · · Score: 4, Insightful

    ...Don't fix it.

    Unless you have a good reason to upgrade, why bother? If this is for a business, and you have no good reason, you have nothing to gain and something (time to upgrade, etc) to lose.

    I'm *not* bashing Apache, which is a damn fine product - but we need to get this 'irrational urge to upgrade' out of our heads.

    --

    I'm not Seth.

  2. Kinda by timbrown · · Score: 2, Insightful

    Just done the upgrade myself, and Apache2 appears fine. HOWEVER, I had big problems with the latest mod_php (4.3.1), they seem to have changed the behaviour of includes, so that when you do an include, the pwd becomes the directory in which the include was located. This breaks a lot of web applications such as phpBB2 and Postnuke. I ended up reverting to an older version of PHP (4.2.1) compiled as a CGI which did the trick fine. IPv6 support sure is nice though!

    --
    Tim Brown