Apache::Application::Plus - Apache/mod_perl integration for CGI::Application::Plus


Included in CGI-Application-Plus 1.21 distribution.

The latest versions changes are reported in the Changes file in this distribution.

The distribution includes:

  • CGI::Application::Plus

    CGI::Application rewriting with several pluses

  • Apache::Application::Plus

    Apache/mod_perl integration for CGI::Application::Plus

  • CGI::Application::Magic

    Template based framework for CGI applications

  • Apache::Application::Magic

    Apache/mod_perl integration for CGI::Application::Magic

  • CGI::Application::CheckRM

    Checks run modes using Data::FormValidator


    Apache/mod_perl 1 or 2
    Perl version >= 5.6.1
    OOTools      >= 1.6
    perl -MCPAN -e 'install CGI::Application::Plus'

If you want to install also all the prerequisites to use CGI::Application::Magic), all in one easy step:

    perl -MCPAN -e 'install Bundle::Application::Magic'
Standard installation

From the directory where this file is located, type:

    perl Makefile.PL
    make test
    make install


   # used instead of CGI::Application::Plus
   use base 'Apache::Application::Plus' ;
   # direct interaction with the Apache request object
   $r = $self->request ;
   %headers = $r->headers_in ;
   # virtual run mode pages
   # instead of using this
   # you can use this


This module is a CGI::Application::Plus sub class that supply a perl handler to integrate your application modules with the Apache/mod_perl server.

Use this module as base class instead of the CGI::Application::Plus, if your application can take advantage from accessing the Apache request object (available as the request property), and/or to run() your application in a handy and alternative way. If you don't need any of the above features, you can use the CGI::Application::Plus module that is however fully mod_perl 1 and 2 compatible.

Note: most of the interesting reading of how organize your application module are in CGI::Application::Plus.

Note: An extremely powerful alternative to this module is the Apache::Application::Magic, that can easily implement a sort of "Perl Side Include" (sort of easier, more powerful and flexible "Server Side Include").

No Instance Script needed

All the generic CGI applications (old, Plus and Magic), use an Instance Script to call the Application Module. The script is usually like this:

    #!/usr/bin/perl -w
    use MyWebApp;                   # the Application module
    my $webapp = MyWebApp->new();   # create a new instance
    $webapp->run();                 # run and produce the output page

With Apache::Application::Plus the Apache/mod_perl server uses the Application module directly (throug the perl handler supplied by this module), without the need of any Instance Script.

The Perl Handler

This module provide a mod_perl 1 and 2 compatible handler that internally creates and run() the Application object, after setting a couple of object properties:

  • request

    This property is set to the Apache request object. Use it to interact directly with all the Apache/mod_perl internal methods.

  • runmode

    The default runmode is set to the base name of the requested filename (e.g. being the requested filename /path/to/file.mhtml, the default runmode will be set to 'file'). Use it as an alternative and handy way to pass the runmode.

Note: Usually you don't need to use neither the perl handler nor these properties, because they are all internally managed.

How to pass the runmode

In a generic CGI Application the run mode usually comes from a query parameter or from code inside your application. Both ways are still working with this module, but you have another way: use the base filename of your links as the runmode.

E.g.: Providing that the RootDirectory of '' has been correctly configured to be handled by your Application module:

Instead of using this (good for any generic CGI application):

You can use this:

Same thing with more query parameters:

Note: Remember that this technique utilize the default runmode. Default means that it is overridable by setting explicitly the runmode inside your code, or passing an explicit 'rm' query parameter. (i.e. if you want to use the provided default, you have just to avoid to set it explicitly).

Apache configuration

The Apache configuration for mod-perl 1 or 2 is extremely simple. In order to use e.g. your Application module, you have to follow these steps:

1 tell mod_perl to load

You can do this in several ways.

In the file (or equivalent) you can simply add:

    use FooBar () ;

or you can tell mod_perl to load it from inside any configuration files:

    PerlModule FooBar

or if your file is not in the mod_perl @INC this will work as well from any Apache configuration file:

   PerlRequire /path/to/
2 tell mod_perl to use it as a (response) handler

In .htaccess file

For mod_perl 1:

    SetHandler perl-script
    PerlHandler FooBar

For mod_perl 2:

    SetHandler perl-script
    PerlResponseHandler FooBar

Note: In order to use this module, the only difference between mod_perl 1 and 2 configuration, is the mod_perl handler name 'PerlHandler' that becomes 'PerlResponseHandler' for the version 2.

3 restrict its use to fit your needs

Use the Apache configuration sections Location, Directory, DirectoryMatch, Files, FilesMatch etc. to restrict the use of the handler (see also the Apache Directive documentation)

   # example 1: httpd.conf
   # only if runs under mod_perl
   <IfModule mod_perl.c>
        PerlModule FooBar
        # limited to the dir /some/path
        <Directory /some/path>
            SetHandler perl-script
            PerlHandler FooBar

   # example 2: /some/path/.htaccess file
   # only if runs under mod_perl
   <IfModule mod_perl.c>
        PerlModule FooBar
        SetHandler perl-script
        PerlHandler FooBar

Note: see also the /magic_examples/perl_side_include/.htaccess file in this distribution.


This module adds just one method to the standard CGI::Application::Plus methods.


This method initializes and returns the internal Apache::Application::Plus object. You can override it if you know what you are doing, or you can simply ignore it ;-).

Note: This method is here just if you need to override the way the module generates the object. Think about this method as it were an included Instance Script that could create the object by setting different properties and/or parameters. Anyway you have alternative methods to change the object properties, such as e.g. the setup() and cgiapp_init() methods.


This module adds just one property to the standard CGI::Application::Plus properties.


This property allows you to access the request Apache object.


If you need support or if you want just to send me some feedback or request, please use this link:


© 2004 by Domizio Demichelis.

All Rights Reserved. This module is free software. It may be used, redistributed and/or modified under the same terms as perl itself.

1 POD Error

The following errors were encountered while parsing the POD:

Around line 292:

Non-ASCII character seen before =encoding in '©'. Assuming ISO8859-1