Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

geoff (2013)

geoff
  reversethis-{gro ... om} {ta} {ffoeg}
http://www.modperlcookbook.org/

see http://www.modperlcookbook.org/~geoff/ [modperlcookbook.org] for personal information, links to presentations, GPG key, and so on.

Journal of geoff (2013)

Monday August 25, 2003
08:37 AM

Apache 2.0.45 left behind

[ #14301 ]
late last week, support for Apache versions older than 2.0.46 was dropped from the development version of mod_perl 2.0. libapreq (which includes the popular Apache::Request) already required 2.0.46, which made that version as good as any to make the break and clean up mod_perl's internals a bit.

so, if you plan on installing the next release of mod_perl 2.0 then you should get busy updating your httpd as well.

and fear not, mod_perl 1.0 still supports many, many different versions of Apache 1.3.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • I guess that rules out people who want to run both PHP and mod_perl, as Apache 1.3 is still the recommended Web server for production PHP applications.

    Of course, this won't affect the large majority of developers who feel the need to choose a side in some sort of imaginary war. :-)

    • Re:PHP (Score:3, Informative)

      mod_perl works fine on Apache 1.3, and that's still the version recommended for production servers anyway.
      --
      • Randal L. Schwartz
      • Stonehenge
    • Re:PHP (Score:2, Informative)

      the move only concerns mod_perl 2.0. mod_perl 1.0 still supports many, many versions of Apache 1.3.

      I'll edit the entry to get rid of the confusion (I hope :)