Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

Perl Errors After Final Install

posted by Krow on 03:45 PM November 30th, 2001   Printer-friendly   Email story
MatchstiK writes "Now that our installation finally worked, our group went to look at the new page we had created. The index.shtml came up fine, but every link to a *.pl file would not load, and came back only as a text file of the perl file itself. What is causing this problem, and how can I fix it?"
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • Sounds like you don't have a Perl handler. You ought to have something like these two directives in your httpd.conf file:
    AddHandler perl-script .pl

    PerlHandler Apache::Registry

    That tells Apache to use mod_perl to process .pl files instead of serving them as raw text.
    • This was absolutely right, nowhere in our conf was a perlhandler. When we put it into our conf file however, each *.pl file was changed from being text, into being a forbidden access! How can that be?
      • There's probably an entry in your Apache or site error log corresponding to the error. Was it a 500 or a 200 or something else entirely?
      • Your setup didn't complete.

        My guess is you didn't Include the slash settings into the main httpd.conf. For a functional site it is absolutely necessary that every f*cking step of the setup is completed successfully!


        -- []: YAGSS - yet another German slash si