Apache 2.0 Goes Gold!

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

not just mod_perl needed

[RoscoeVill]

What about appropriate version of tomcat? I'm hoping that since there is real current dev on that at the moment, that it should work when I try later this weekend.... but all the jakarta doc says apache 1.3...

Any one try it yet?

Configuration, setup?

[Phroggy]

What do I need to know about upgrading from 1.3 to 2.0? What's different in the configuration? Any changes in the way the files are laid out by default? Will my existing httpd.conf work without modification? Would that be a stupid thing to try?

I thought I heard somewhere that 2.0 might make it possible to have PHP scripts with per-user permissions, like you can get CGI scripts to do if you use suEXEC to setuid to the appropriate user before executing. This is important for servers with multiple users running their own web sites; even if all your users are trusted not to mess with each other's stuff you can run into icky situations where a PHP script writes to a file that the user then doesn't have FTP access to (so they have to write another PHP script to access it). Did I hear correctly? If so, what's involved in configuring it? If not, does anyone have any workarounds?

Re:PHP not there yet

[Kwikymart]

Yes, but there are some of us that like to use STABLE code. It's not really php's fault though. *sigh* this is probably a useless argument, however, because of the fact that this is fundamentally a x.0.0 release (even though its really 2.0.35). I am not going to run it till it has spent some time in the field (or I may set it up on an extra non-production machine). Damn, php rules for small applications.

Re:I'll use it when Debian packages it.

[Slash Veteran]

me too. I don't need freshmeat-type announcements (though I don't mind them, guys). But Debian is my preferred delivery system.

If you're not using Debian, you're wasting your time -- literally.

Re:Watch Software Update

[cpeterso]

I seriously doubt Apple would "slipstream" Apache 2.0 onto users' computers via Software Update. Apache 2.0 breaks backwards compatibility on many Apache modules and who know what else. Since Apache 2.0 is largely untested by the public, I bet Apple will wait for a few more updates and then include it later in Mac OS X 10.2.

apt-get

[MikeyO]

The obvious missing option for me is:

I'll run apache 2.0 when apt-get upgrade decides i will.

i'll run it when...

[Bandito]

debian packages it up for download.