in reply to Re: CGI or CGI::Fast
in thread CGI or CGI::Fast

Many thanks, Alexander!

I was a bit surprised there wasn't a simple way to test and I'm thankful for your code. I ran your code on my local server and on the server at the hosting end (I have an existing plan). The good thing is the code works like a champ but the bad thing is that both the local and production servers don't support CGI::Fast :(

Well, at least now I can put that thought of using CGI::Fast aside and be content with just CGI :)

Replies are listed 'Best First'.
Re^3: CGI or CGI::Fast
by afoken (Chancellor) on Sep 12, 2012 at 18:56 UTC

    Running programs as FastCGI instead of CGI typically requires some webserver configuration. The mod_fastcgi plugin for Apache offers different options:

    • Have a custom program file extension, like .fcgi or .fpl. This is configured via AddHandler.
    • Have a special location reserved for FastCGI programs (comparable to the typical /cgi-bin/ location). This is configured via SetHandler.
    • Have a special location (URL prefix) reserved for a single FastCGI program under control of the Apache server. This is configured via FastCGIServer.
    • Have a special location (URL prefix) reserved for a single FastCGI program controlled by some other program (init, daemontools, ...). This is configured via FastCGIExternalServer.

    When you place a FastCGI capable CGI program in /cgi-bin/ (or any other location configured for CGI scripts), it will run in CGI mode, not in FastCGI mode. The same happens when the program name ends with .cgi (or any other extension mapped to plain CGI).

    So, perhaps renaming or moving your program may be sufficient. Ask the webserver administrator / hoster support.

    Alexander

    --
    Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
[reply]
[d/l]
[select]

In Section Seekers of Perl Wisdom