----- Original Message ----- 
From: "Devin B. Hedge" <[EMAIL PROTECTED]>
To: "'Robert J Taylor'" <[EMAIL PROTECTED]>
Sent: Wednesday, September 17, 2003 3:38 PM
Subject: RE: Apache 1.3 config problem


> Robert,
> Thanks for your help. I've been struggling with describing my intent for a
> few days. Let me see if I can clear it up.
>

Sorry, I've been in Sequoia National Park / Forest for the past few days and
decided to not try to catch up with what I missed. I saw this as the first
post.

> I'm trying to run Perl scripts (*.pl) using mod_perl.
>

Aha! Question: does your hosting provider have mod_perl built into Apache
(statically or linked dynamically) or did you do it for them?

> The index.pl file is in the htdocs directory. It is not in its own
directory
> structure.
>

No problem. Although I recommend PerlRun versus Registry for handling
unweildy CGI-Scripts written in Perl gracefully.

Try this (untested - I use a similar setup using the Directory section, but the File 
section should work similarly; it matches based on the regex you specify). You do need 
to use the PerlModule statement...

PerlModule Apache::PerlRun # or put this in httpd.conf before including your virtual 
host directory
<FilesMatch "\.pl">
    SetHandler perl-script
    PerlHandler Apache::PerlRun
    PerlSendHeader On
    PerlSetVar PerlRunOnce On
</FilesMatch>


> so I'm trying to run http://www.devinhedge.com/index.pl from
> /home/devin-com/public_html/index.pl
>
> I think I posted the incorrect configuration file. I'm not using /perl as
a
> Location. I did that to try and move index.pl around to see if it
mattered.
> The correct location would be the root of the ~/html_public directory.
>
> The current behavior is that Apache just serves index.pl as a text file to
> be downloaded.
>
> Devin.
>

Robert

Reply via email to