BaldPenguin has asked for the wisdom of the Perl Monks concerning the following question:

Trying to take advantage of the FastCGI installed on my hosting box, I took my modules which worked under the normal CGI::Application and simply changed the base statement to use CGI::Application::FastCGI. The result is that I have nothing in my CGI parameters when the form using a POST method, all is normal if it does a GET.

Has anyone else seen this behavior? Is there a patch I can place in there?

I can provide the code, but it looks just like the pod.

Don
Everything I've learned in life can be summed up in a small perl script!
  • Comment on Lost query in CGI::App::FastCGI on POST

Replies are listed 'Best First'.
Re: Lost query in CGI::App::FastCGI on POST
by greatshots (Pilgrim) on Nov 22, 2006 at 02:05 UTC
    From basic understanding on perl CGI, I could say that the above replacement won't work as you expect. Have you read any manual which says about CGI::Application -> CGI::Application::FastCGI ?
    Update 1 - Begin
    Have you happened to see the below note ?
    Note that cgiapp_init() will be called only once under lifecycle of FastCGI. setup() will also only be called once. (you should not be doing magical things in 'setup'.) So if you want to do something for every REQUESTS, you should write the logic in cgiapp_prerun().
    reference
    Update 1 - End
[reply]

      From the documentation for CGI::Application::FastCGI:

      Inherit this module instead of CGI::Application if you want to run your cgi programs based on CGI::Application under FastCGI.
      DWIM is Perl's answer to Gödel
[reply]
      All of my logic is occurring in the run mode itself, GET and POST variables should not be locked within the cached lifecycles. If that were the case, why does the GET work when the POST does not?

      Don
      Everything I've learned in life can be summed up in a small perl script!
[reply]

Back to Seekers of Perl Wisdom