Question

I use Apache 1.3.27 with mod_perl (perl 5.8.0 library) in and the newest Beta TWiki. My question is about the SetHandler Apache option. If I use SetHandler cgi-script, it will execute TWiki's 'configure' script in /bin, but report not using mod_perl, or report the perl version in the scripts header (/usr/bin/perl, being an old system perl). If I use SetHandler perl-script, it will not execute 'configure' just display the code text. If I rename it to 'configure.pl', it gets executed and mod_perl is reported to be used. I never saw a wiki topic, that said I have to rename the scripts to .pl versions, despite perl-script being used. Do they have to be renamed to work properly with mod_perl? Now I'm confused ....

Environment

-- PhilippeSteindl - 13 Oct 2005

Answer

If you answer a question - or have a question you asked answered by someone - please remember to edit the page and set the status to answered. The status is in a drop-down list below the edit box.

See Step 3 of the TWiki Installation Guide where it talks about renaming files. Clearly on your setup you need to rename the files to end in .pl in order for them to work with ModPerl.

Also, there are serious security issues with TWikiRelease02Sep2004 - please see TWikiSecurity and update to TWikiRelease04Sep2004, even if you are on an intranet.

By the way, Perl 5.8.0 is a very old version that you may want to upgrade if you run into problems. As long as your locale environment setting does not include .utf8 at the end, you should be OK, but see IssuesWithPerl5dot8 if you have any issues with this.

-- RichardDonkin - 13 Oct 2005

So that I did not have to rename files, I added the following to my VirtualHost defninition:

    <Directory ~ /bin/>
        SetHandler perl-script
        PerlInitHandler Apache::StatINC
        PerlHandler Apache::Registry
        Options ExecCGI
    </Directory>

-- MichaelGrant - 13 Mar 2006