Re^2: STDIN refuses input

Well, I said I am a beginner, and it certainly shows as I do not understand many of the comments. Let me try again.

I copied three sample Perl scripts from the Web, because I wanted to know how to install them on my host's system. Two of three scripts were put into my host's CGI-BIN and worked perfectly. The other script was also installed and works to a point.

It is a simple script and I expected it would ask for input through <STDIN> and save the input in a $variable. The script would then immediately print "Hello, $variable." I am sure that <STDIN> does not wait for input and prints the incomplete hello message without the $variable.

From what I understand, I could achieve this test with only my local computer. That is not what I need. I got the installation correct, I think, but I am missing something. Perhaps the script I copied is meant for a local computer.

Ultimately, I have some pre-written scripts that I want to use, and I need to know how to modify them for my site, and install them.

What will it take to make my simple script work correctly? As soon as it works, I will go on to learn something more difficult.

Thanks to all.

lcole

Comment on Re^2: STDIN refuses input

Replies are listed 'Best First'.
Re^3: STDIN refuses input by taint (Chaplain) on Dec 16, 2013 at 21:37 UTC
Greetings, lcole. If I understood you correctly, I've already given you pretty much what you asked for; Take input from a web page, and respond to said input. There are other possible variations. The way I chose to present it, was what I thought might be easiest to follow, and seemed closest to the example you presented. From the looks of it (your script), it seems pretty old, in style. Usually taking input from `<STDIN>` is chosen when you are at a console, or tty/terminal (at a local computer -- within a shell). You can still use that same process within a web page. Something like `read(STDIN,$temp,$ENV{'CONTENT_LENGTH'});` [download] But it can get pretty hairy. Because you must take additional measures to "sanitize" your input. To prevent users from entering shell commands like rm `-rf /`. Which could effectively delete your(hosters) file system. The commands are only limited to what is available with your hosting account, or how clever the user is, that uses your (unsanitized) input. So given that you indicate that you're fairly new to Perl. I would strongly advise against taking the `<STDIN>` approach. At least until you become more comfortable with Perl. But by then, I suspect you'll see that's it's probably more work than it's worth. Just to say you did it with `<STDIN>` :) Hope this helped, and best wishes. --Chris Yes. What say about me, is true.	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: STDIN refuses input
by taint (Chaplain) on Dec 16, 2013 at 21:37 UTC

lcole

If I understood you correctly, I've already given you pretty much what you asked for; Take input from a web page, and respond to said input.

There are other possible variations. The way I chose to present it, was what I thought might be easiest to follow, and seemed closest to the example you presented.

From the looks of it (your script), it seems pretty old, in style. Usually taking input from <STDIN> is chosen when you are at a console, or tty/terminal (at a local computer -- within a shell). You can still use that same process within a web page. Something like

read(STDIN,$temp,$ENV{'CONTENT_LENGTH'});
[download]

shell

-rf /

strongly

<STDIN>

Hope this helped, and best wishes.

--Chris

Yes. What say about me, is true.

[reply]
[d/l]