in reply to Issue with Running Long Processes thru CGI

Hello sara2005,

I'd suggest something like

{ foreach my $p (param()) { warn "param $p = '".param($p)."'\n"; } } # The execution enters this loop in the first pass whereas it should n +ot!!! if (my $session = param('session')) { # returning to pick up session d +ata
and check the apache error_log to see what's actually set at that time. Then work back in your code and see where it comes from...

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Replies are listed 'Best First'.
Re^2: Issue with Running Long Processes thru CGI
by Anonymous Monk on Jul 03, 2006 at 13:25 UTC

    I included the lines to print out the parameters and checked the error log as well but couldn't figure out what is going wrong

    It prints a session id which I am not able to locate in the /tmp/FileCache folder...

    still checking out...

      Could it be that the session id is passed in from the client? I would put the parameter printing code at the very beginning of the request handler / your cgi script, to see what's actually coming in.

      --shmem

      _($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                                    /\_¯/(q    /
      ----------------------------  \__(m.====·.(_("always off the crowd"))."·
      ");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

        Thanks for your suggestions on this issue.

        I tried today without changing anything and it works fine!!!

        I am confused as to why it failed yesterday but worked fine today. This is scary because it could potentially come back to haunt me..

        I am not sure if it is anything to do with Unix OS

        Anyway, for now I am going ahead with it and troubleshoot, if it occurs again