in reply to Re^2: Running a CGI script from a command line?
in thread Running a CGI script from a command line?

A fun approach; maybe overkill here. It’s multi-arg system that avoids the shell, not capture.

Well sure :) but if you don't capture it, it just goes into the regular place, at which point, the question becomes, why not do a redirect instead?

Oh right, the OP didn't ask that exactly, that was just the question that brought me to this question (from a cgi execute another cgi) ... looked close enough :)

  • Comment on Re^3: Running a CGI script from a command line?

Replies are listed 'Best First'.
Re^4: Running a CGI script from a command line?
by shanen (Initiate) on Jun 16, 2015 at 06:40 UTC
    I am doing some sort of redirect, in that the HTML output of the original PERL file is properly captured into a file that I can then load in a browser.

    I think I am skipping over some extremely low level of ignorance here. The answer is doubtless "intuitively obvious to the most casual observer", but I am evidently too tense?

      I am doing some sort of redirect, in that the HTML output of the original PERL file is properly captured into a file that I can then load in a browser.

      I think I am skipping over some extremely low level of ignorance here. The answer is doubtless "intuitively obvious to the most casual observer", but I am evidently too tense?

      So have you considered installing a webserver to run your "cgi" ?

      apacheet (Plack::App::CGIBin),

        Yes, but the option of running unofficial servers is no longer permitted here. Official servers require extensive approvals. Mostly bean counters, but also security people.

        In today's session I continued the experiments from last night on the other machine. Then I read and meditated over the RFC for a while. I also started poking about in the ancient code, both my own and some of the inherited fragments. My results seem to be going backwards.

        Freedom = (Meaningful - Coerced) Choice ≠ (Beer | Speech)