Emulating a CGI environment is rather trivial. You basically just need to set the following ENV variables and optionally pipe something to it via stdin. Also note you need to modify the ENV before you fork. 
sub run_local
{
  local %ENV;
  %ENV = qw/foo bar baz etc/;
  open my $script, "perl foo.pl |" or die $!;
  print $script $CONTENT;
  my @return = <$script>;
  close $script;
  return @return;
}

[download]
The full list of CGI vars follows: 
The following environment variables are not request-specific and are s
+et for all requests:

    * SERVER_SOFTWARE

      The name and version of the information server software answerin
+g the request (and running the gateway). Format: name/version

    * SERVER_NAME

      The server's hostname, DNS alias, or IP address as it would appe
+ar in self-referencing URLs.

    * GATEWAY_INTERFACE

      The revision of the CGI specification to which this server compl
+ies. Format: CGI/revision

The following environment variables are specific to the request being 
+fulfilled by the gateway program:

    * SERVER_PROTOCOL

      The name and revision of the information protcol this request ca
+me in with. Format: protocol/revision

    * SERVER_PORT

      The port number to which the request was sent.

    * REQUEST_METHOD

      The method with which the request was made. For HTTP, this is "G
+ET", "HEAD", "POST", etc.

    * PATH_INFO

      The extra path information, as given by the client. In other wor
+ds, scripts can be accessed by their virtual pathname, followed by ex
+tra information at the end of this path. The extra information is sen
+t as PATH_INFO. This information should be decoded by the server if i
+t comes from a URL before it is passed to the CGI script.

    * PATH_TRANSLATED

      The server provides a translated version of PATH_INFO, which tak
+es the path and does any virtual-to-physical mapping to it.

    * SCRIPT_NAME

      A virtual path to the script being executed, used for self-refer
+encing URLs.

    * QUERY_STRING

      The information which follows the ? in the URL which referenced 
+this script. This is the query information. It should not be decoded 
+in any fashion. This variable should always be set when there is quer
+y information, regardless of command line decoding.

    * REMOTE_HOST

      The hostname making the request. If the server does not have thi
+s information, it should set REMOTE_ADDR and leave this unset.

    * REMOTE_ADDR

      The IP address of the remote host making the request.

    * AUTH_TYPE

      If the server supports user authentication, and the script is pr
+otects, this is the protocol-specific authentication method used to v
+alidate the user.

    * REMOTE_USER

      If the server supports user authentication, and the script is pr
+otected, this is the username they have authenticated as.

    * REMOTE_IDENT

      If the HTTP server supports RFC 931 identification, then this va
+riable will be set to the remote user name retrieved from the server.
+ Usage of this variable should be limited to logging only.

    * CONTENT_TYPE

      For queries which have attached information, such as HTTP POST a
+nd PUT, this is the content type of the data.

    * CONTENT_LENGTH

      The length of the said content as given by the client.

[download]

In reply to Re: HTTP::Request to local script by BUU
in thread HTTP::Request to local script by mirod

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.