Re: Embedding "user" CGI output into a mod

To customize the response to the browser, you will need to capture the output from the cgi script. For cgi scripts at another machine, your Apache handler will in affect act as a forward proxy to the request: it will send the request with LWP::UserAgent and capture the output with LWP::Response.

There is no difficulty if you know the Apache API. Just ensure sure that all incoming and outgoing headers are copied, especially the HTTP headers that may appear twice, like Cookie -- you cannot use functions like $r->headers_in that return hash structures, thus suppressing the second Cookie header.

Comment on Re: Embedding "user" CGI output into a mod_perl response

Replies are listed 'Best First'.
Re^2: Embedding "user" CGI output into a mod_perl response by bmcatt (Friar) on May 10, 2006 at 01:38 UTC
This is actually going to be for cgi scripts that are deployed (in the current "old" system) on the same system, so there's no need to act as a full proxy. Theoretically, I should be able to just use some aspect of the Apache interface(s) to fire off the CGI script "inline" and then extract the body of the response. Thanks for the suggestion, though. I'd already thought of proxying it, but that then leaves me needing to have an exposed (in the sense of publicly-visible) cgi interface and I'm explicitly trying to avoid that.	[reply]

Replies are listed 'Best First'.

Re^2: Embedding "user" CGI output into a mod_perl response
by bmcatt (Friar) on May 10, 2006 at 01:38 UTC

Thanks for the suggestion, though. I'd already thought of proxying it, but that then leaves me needing to have an exposed (in the sense of publicly-visible) cgi interface and I'm explicitly trying to avoid that.

[reply]