Slashdot Mirror

← Back to Stories (view on slashdot.org)

Apache HTTP Server 1.3.31 Released

Posted by michael on from the nice-feather dept.

efranco writes "Apache Software Foundation had released today a new version of the 1.3.x Apache webserver branch. How long this branch will last? Despite the interesting new features introduced in the 2.0.x branch, it seems that the branch 1.3.x is still the most used around the world." Errr, is PHP playing nicely with Apache 2 yet?

5 of 56 comments (clear)

  1. 1.3.31? by platipusrc · · Score: 2, Interesting

    I generally run the latest version of major software that I use, and I use Apache's httpd. The version I'm running today is 1.3.29. Did they skip 1.3.30, or was it a silent buggy release...or is the story a typo?

    --
    And the muscular cyborg German dudes dance with sexy French Canadians
  2. Re:Don't bother looking or anything by justMichael · · Score: 3, Interesting
    No. It says "Do not use Apache 2.0 and PHP in a production environment neither on Unix nor on Windows."
    That document is also almost 9 months old, to the day: Last updated: Sat, 09 Aug 2003.

    I have numerous sites running apache2 and PHP and have had no problems.

    The only issue I have is no mod_throttle, and I'm not the guy to try and port it to the 2.x API ;)
  3. Re:PHP works fine with Apache 2.0 by sweede · · Score: 2, Interesting

    I personally am waiting for the perchild to be fixed so i can run php in virtual hosts as the user instead of running as apache like suexec does. Having everything group writeable for applications like Gallery sucks as someone could exploit that and delete my photo gallery or who knows.

    --
    I follow the SDK and GDN principles.. Spelling Dont Kount, Grammer Dont Neither
  4. Yes, Virginia, there is a PHP by aminorex · · Score: 3, Interesting

    My employer has been using 2.0.40 with php 4.2.2
    for a coon's age. Ignore the scarewords. (Yes,
    using non-threadsafe 3d party libraries with a
    multithreaded application execution model is prone
    to bugs... so don't do that, doh!)

    --
    -I like my women like I like my tea: green-
  5. The reason: API stability/compatability by moeymo · · Score: 3, Interesting

    If you've highly customized instance of Apache, the configuration API changes make it expensive to upgrade.

    You can stay in the old branch or spend hours figuring out how to do the same thing with the latest version. People take the old until they need new features in the new version.

    The good news is that Apache is stressing that configuration/public APIs need to be more stablea across versions. Thank you!