Re: CGI from another script

that is a valid way to call a cgi script from the command line so we'd need to see "some_script.cgi" to be able to tell why it's not working.

On another note, are you calling this second cgi script with backticks? I've never seen this as a good idea - everytime it's either needed changed into a module, called with a form, or ran using a redirect. So if you could give your reason for using backticks maybe we could find a better solution.

"Cogito cogito ergo cogito sum - I think that I think, therefore I think that I am." Ambrose Bierce

Comment on Re: CGI from another script

Replies are listed 'Best First'.
Re^2: CGI from another script by rsiedl (Friar) on Sep 03, 2005 at 06:41 UTC
Hi, thanks for your reply. I'm not sure I follow what you mean by "everytime it's either needed changed into a module, called with a form, or ran using a redirect". Isnt backtick and system() both the same, or are you saying its a bad idea to use either of these fullstop? The reason I am using this method is because I have some scripts which i need the output from. Ideally I want to rewrite them in module format but at the moment dont have the time.	[reply]
Re^3: CGI from another script by kutsu (Priest) on Sep 06, 2005 at 14:50 UTC
backticks and system are not the same (seeing as you want to capture the output backticks is proably what you want) but yes using system or backticks always opens up a potential security hole anytime it's used (not to say it can't be closed). The main point is that a cgi script where a module is needed is confusing and harder to maintain - I just wanted to make sure you were aware of this. Though make sure the script is read-only as you are calling it with 'perl ...' and this will prevent it from being called through the webserver. "Cogito cogito ergo cogito sum - I think that I think, therefore I think that I am." Ambrose Bierce	[reply]