Late to the question, but don't discount using a simple (pre-formatted)
tag either ... keeps things lined up nicely in a mono-spaced font. I often use this
for short web-ified shell cmd results.
#!/usr/local/bin/perl -w
print "Content-type: text/html\n\n";
our @cmd = `df -sk|fgrep -v nf
o click a Save or
Open dialog box, and then the data is loaded into Excel as a CSV very nicely.
They then have to know what to do when Excel asks them if they save it (xls vs. csv
something something).
This may not be an option if your users have not been gifted with "clue",
You also might want some background on the HTTP header field for Set-Cookie - sort of
behind the scenes of what the CGI module does.
I'd suggest some research for "RFC 2109" and "http set-cookie". I found this helpful
to understand the simple cookie header-field syntax, separate from the CGI met
Also, some proxy servers (notably AOL) ignore HTTP_EQUIV directives set in META tags.
aol HTTP header info:
http://webmaster.aol.com/index.cfm?article=556&expand=0&sitenum=2&menuid=56
>>> Bob Showalter <[EMAIL PROTECTED]> 8/25/2002 4:11:25 PM >>>
> -Original Message-
> From:
I am putting a CGI around an existing process that had been done manually (command
line) in the past.
The last piece of the process is to use PGP by user 'dick'. User 'dick' has a keyring
of keys, one of which is the key for the user-id of someone we want to share files
with, say, 'Acme Dist.
He is correct.
-Original Message-
From: Inspirational Michael [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, October 10, 2001 12:57 PM
To: [EMAIL PROTECTED]
Subject: Of this Shit
Brother I understand that may work in most instances, but, believe me, I
have worked with Randal on this and be
