httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chuck Murcko <>
Subject Re: [2.0] proposed vhost config rewrite
Date Wed, 11 Jun 1997 03:40:01 GMT
Doug MacEachern wrote:
> Rob Hartill <> wrote:
> > My httpd.conf currently contains an embedded Perl script (thanks to
> > mod_perl). I wouldn't expect Apache to use Perl, not because it isn't
> > a good solution, but because it won't suit everyone and it'll be a
> > bugger to get working on everyone's systems. The above would let me
> > use a Perl config compiler and someone else a Java one...
> I wouldn't say bugger to get working, Perl is quite easy to install.
> Although Perl might not be well suited for everyone, it's *very* well
> suited as a glue language, not to mention it's been ported to almost
> every platform you can think of.  Judging from the recent discussion
> I've seen here, I think it's worthwhile for folks to have a better
> understanding of what we can currently do with Perl code inside apache
> config files.  Some copy-n-paste from mod_perl.pod:
> (sorry this is long)
> ---
> With <Perl></Perl> sections, it is possible to configure your server
> entirely in Perl.
> <Perl> sections can contain *any* and as much Perl code as you
> wish.  These sections are compiled into a special package who's symbol
> table mod_perl can then walk and grind the names and values of Perl
> variables/structures through the Apache core config gears.    Most of
> the configurations directives can be represented as C<$Scalars> or
> C<@Lists>.  A C<@List> inside these sections is simply converted into
> a single-space delimited string for you inside.  Here's an example:
This is actually nicer that what some other servers do with Python.
Chuck Murcko
The Topsail Group, West Chester PA USA

View raw message