Running Perl Scripts

WampDeveloper is primarily a PHP web-server, but it does come with Perl (StrawberryPerl distribution), and is able to run perl scripts out-of-the-box.

Simple Perl Scripts

For simple perl scripts (not entire perl based applications), just place the perl scripts into the website’s already existing \cgi-bin folder (it is outside of \webroot) -

Then you can access those scripts via URL -

Entire Perl Applications

For more complicated perl applications -

Because of the size and complexity of some perl applications, it’s not going to be good enough to place those perl applications into the website’s default \cgi-bin folder… We’ll rather have to place the application into the website’s \webroot folder, and enable CGI execution in the application’s folder…

Edit the website’s VirtualHost file (select website in Websites Tab, click VirtualHost buttons), inside the <VirtualHost> block add in…

<Directory "C:/WampDeveloper/Websites/">
    DefaultType text/html
    Options -Indexes +ExecCGI
    AllowOverride None
    Order allow,deny
    Allow from all
    SetHandler cgi-script .pl

Also, inside the above Directory block in the HTTPS VirtualHost, add line:
SSLOptions +StdEnvVars

Save files. Restart Apache.

If Apache won’t start, from the command-line (button in System Tab), run -

httpd -t -n "Apache2"
httpd -k start -n "Apache2"

This will tell you which lines in the VirtualHost file have errors in them.

Extra Perl Modules

Some perl applications might also require extra perl modules to be installed. To do so, open the command-line (button in System Tab) -

Then run something similar to this (substitute in package-names) -

perl -MCPAN -e shell;
install package::name1
install package::name2

This might, or might not, work out well – depending on the extra modules and what they require.

One thought on “Running Perl Scripts

  1. admin Post author

    WampDeveloper’s configuration (Config\Apache\extra\wampd-cgi.conf) defaults to using:
    ScriptInterpreterSource Registry-Strict

    Registry-Strict” does not attempt to read the “shebang” line (path to interpreter) of each script. Instead, it uses the script interpreter as defined in the Registry per the given file extension (*.pl).

    When WampDeveloper is installed, it sets in the Registry:

    Key: HKEY_CLASSES_ROOT\.pl\Shell\ExecCGI\Command
    Value name: (default)
    Value type: REG_SZ
    Value data: C:\WampDeveloper\Tools\Perl\perl\bin\perl.exe

    If you need to execute *.cgi files as perl scripts:
    1. Update Configuration:
    SetHandler cgi-script .pl .cgi
    2. Set Registry Key/Value:

    If you need to use another interpreter, and/or the “shebang” line, you’ll have to set ScriptInterpreterSource in the Directory block…
    ScriptInterpreterSource Script

    And set the proper “shebang” line (that contains proper path to interpreter) in each script file.

    The “shebang” line is 1st line of script that provides the path to the script interpreter with form (using forward-slashes):


Leave a Reply

Your email address will not be published.

You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>