Slashdot Mirror

← Back to Stories (view on slashdot.org)

Apache 2.0 Goes Gold!

Posted by krow on from the hell-freezes-over-news-at-5 dept.

The Apache Software Foundation's Apache HTTP Server, version 2.0.35, has now been released for General Availability. You can find the official announcement, and download the server, from their website. Be sure to try a mirror first. Congratulations to the HTTP Server Project for getting the final release out. If you are wondering about it being usable in a production environment, you should poke around Slashdot's servers and see if you are surprised (now if only mod_perl was finished we could move more of our servers over to using the new release).

The HTTP Server Project is now recommending this release for use on production websites. 2.0.35 is now considered their best release and should be used in preference to all older versions (including the 1.3 series). A few of the new features are:

  • higher performance over 1.3
  • multiple operational models: threaded, hybrid multi-processes and multi-threaded
  • specific request processing for Windows, Netware, BeOS, and OS/2
  • integrated SSL and WebDAV support
  • improved HTTP proxy support
  • I/O layering and filtering

3 of 325 comments (clear)

  1. PHP not there yet by augustz · · Score: 5, Informative

    Upgrades are a little early unless PHP starts compiling in, especially statically. (A la mod_php without DSO). They're getting close, php 4.2.0 should work I suspect, whenever it or any other previewish release comes out.

    Also, be nice to get some good benchmark numbers. Speed / SSL / Dynamic Content seem to be things just about everyone relies on, and it'd be great to have a nice case to move from 1.3. I know the Apache team has made a lot of progress on this, be great to see it validated.

    Bravo all around of course.

    - August

  2. Re:Configuration, setup? by cliffwoolley · · Score: 5, Informative
    Check out my Linux Magazine article from January, which was just posted online recently.</shameless plug>

    The short answer to your question: while yes, you can probably get your 1.3 config to work without *too* many changes, you should spend a bit more time exploring Apache 2.0, or you'll miss out on a lot of the benefits.

    The configuration is totally different; it uses GNU autoconf now instead of the home-grown APACI system. The two have many similarities, but you should peruse all of the

    ./configure --help
    options carefully.

    The perchild MPM (which provides the configurable userid per Apache child process that you mention) is possibly not yet working; it's still classified as experimental. But we'll probably be getting that cleaned up within another release or two.

  3. Semi-stable working PHP by SiMac450 · · Score: 5, Informative
    Well, neither 4.1.2 or 4.2.0RC2 worked for me with Apache 2.0. However, I have a simple solution. I just stole the CVS copy of the apache2filter (well, actually only the .h, .c, and .m4 files) and put it with 4.1.2 and it works perfectly. See it in action at http://simonster.com/. If you're too lazy to do this procedure yourself, I have a source archive at http://simonster.com/php-4.1.2.tar.gz

    For installation, I found that the easiest thing to do is to add

    AddOutputFilter PHP .php
    AddInputFilter PHP .php

    Somewhere in the document and, for indexes,

    AddType text/html .php

    before the DirectoryIndex (which must be modified to add index.php). The CVS version works also, but I had problems with some scripts under it. Hope this helps. SiMac450