Re: CGI scripts

[matthew sporleder <msporleder%gmail.com@localhost>]

On Sun, May 8, 2011 at 9:05 PM, Steven Bellovin <smb%cs.columbia.edu@localhost> 
wrote:
>
> On May 8, 2011, at 8:37 34PM, George Michaelson wrote:
>
>> On Sun, 08 May 2011 16:30:13 +0300, Jukka Ruohonen wrote:
>>
>>> On Sun, May 08, 2011 at 08:16:40AM -0400, matthew sporleder wrote:
>>>> I think the usual suspects of "printenv" and "hello world" would be
>>>> appropriate.
>>>
>>> No offence, but I think a "hello world" would be an insult to the
>>> intelligence of the current user and developer base. I was thinking more
>>> about something with real value. Something that would utilize
>>> NetBSD-specific features. Something that you could actually run on your
>>> own NetBSD server/router/appliance/whatever.
>>>
>>> - Jukka.
>>
>> I'd like the option to be insulted please.
>>
>> the great thing about 'Hello world\n' examples is that they are sentences
>> in Computer Science my brain is pre-wired to expect to understand.
>>
>> So, please, *insult me* -Its what I'm used to :-)
>>
> A "Hello word\n" script is fine for showing the very basics.  But what I'd
> like to see are simple examples that deal with inputs of three different
> types: context (e.g., HTTPS info or remote IP address), parameters passed
> via the URL (http://www.netbsd.org/foo?bar=yes+bletch=no), and parameters
> passed via a submitted form.
>>
>
>

In general, "hello world" in CGI would say something like;

Enter your name:
[               ]
[Submit]

(click)

Hello, $name<br />

---

printenv should show any params passed and where they ended up.

---

File upload (the third thing I suggested which has been deleted from
this thread) would also show an important feature of whatever cgi lib
we're including, if any at all.