since i wanted to hang the demo on how to pack Params
as paragraphs - also took the side adventure to show
how '\r' is dealt with on mac and linux boxes - so
you can clean them out of the input stream before going on.
http://www.wetware.com/drieux/pbl/cgi/ParseParmsToPara.txt
ciao
drieux
---
On Monday, May 20, 2002, at 11:22 , David vd Geer Inhuur tbv IPlib wrote:
> $icname = "123qwerty&";
quotes interpolate - single quotes do not;
try
my $allow='A-Za-z0-9_.';# what we allow
my $icname = '1+23|qwerty&';
if (!($icname =~ /^[$allow]+$/)) {
--- drieux <[EMAIL PROTECTED]> wrote:
> ...
>
http://www.wetware.com/drieux/pbl/cgi/ParseParmsToPara.txt
>
>
> ciao
> drieux
Thanks to all who contributed to this thread. Here's
what I finally ended up using, incorporating several
of your suggestions (HTML tags in code):
my $eol = chr(13) . c
--- Octavian Rasnita <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I know how to open and print an html or text
> document on the screen if the
> file is on my site and I know the real path to the
> file.
> I want to open and print a document on the screen
> but it is not on my site
> and of course, I
> -Original Message-
> From: Jake [mailto:[EMAIL PROTECTED]]
> Sent: Monday, May 20, 2002 5:18 PM
> To: John Brooking; Beginners CGI
> Subject: Re: Translating newlines to HTML paragraphs
>
> ... My guess though is that textarea newlines will get sent
> as cr/lf no matter what OS the cli
on Tue, 21 May 2002 12:35:59 GMT, [EMAIL PROTECTED] (Bob
Showalter) wrote:
> This is dependent on the browser, and not the client OS. The
> HTML standard would be controlling here, and it's pretty
> vague if you look at the TEXTAREA section.
It was somewhat less vague in the 'HTML 3.2 Referenc
HI,
I'm creating a CGI script in perl for my web page. When I bring it up in IE
6 it displays beautifully, however, if I open it in Netscape 6, the cgi
script runs but Netscape, instead of showing the web page, shows the text of
the page (the html code) that my CGI script produced with the corr
is this URL externall visible so we can look at it?
Failing that can you copy in your EXACT code please?
have you ran through a proxy (such as http sniffer) so you can see exactly
the HTTP conversation that takes place?
It sure as heck looks like NS is being stricter about processing the
header
How about using LWP?
# Create a new agent object
use LWP::UserAgent;
$ua = new LWP::UserAgent;
$ua->agent("SomeAgentName/0.1 " . $ua->agent);
# Create a request (HTTP,FTP,File)
my $req = new HTTP::Request GET => 'http://www.insiteful.tv';
# Pass request to the user agent and get response
my $re
It is possible that you are printing the HTML header twice, although I can't
tell because we can't see the rest of your code. Exploder actually handles
that situation a little more gracefully than Netscape if that is indeed your
case...I can't tell based on the info provided though. Make sure that
> if (!($icname =~ /^[$allow]+$/)) {
> print "your IP-Block name cannot contain special characters\n";
> print "we do not like <$1> \n" while ( $icname
> =~ m/([^$allow])/g);
> }
You could use the !~ operator to negate this automatically and print it
in a one-shot
Hi all.
Thanks for the sanity check. I was printing a line of debugging before the
content-type output line. Commenting that out fixed it. IE was smart
enough to ignore it, while Netscape preferred to reject the page.
Thanks again,
Phil
-Original Message-
From: Scot Robnett [mailto
That depends on how you look at it...Netscape was the browser that actually
forced your hand to clean up the code, so which browser was smarter? :)
Scot Robnett
inSite Internet Solutions
[EMAIL PROTECTED]
[EMAIL PROTECTED]
-Original Message-
From: Phil Fickas [mailto:[EMAIL PROTECTED]]
Hi
As a developer I won't agree that IE is smart because it lets programmers
ignore minor mistakes.
It allows you to be a negligent programmer.
Always use netscape for testing because that's the real test. Then use IE -
that's what the most of the world uses after all!!!
Thanks
Aman
- Origina
Scot's right Phil, IE wasn't being 'smarter' it was being 'slacker'
:-)
joel
-Original Message-
From: Scot Robnett [mailto:[EMAIL PROTECTED]]
Sent: 21 May 2002 15:11
To: Phil Fickas; [EMAIL PROTECTED]
Subject: RE: Netscape vs. IE Discrepancy FIXED
That depends on how you look at it...
Yea, I see that. I'm still hitting my self over here after realizing that I
called a Microsoft product "smart"...:-(
--Phil
-Original Message-
From: Joel Hughes [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 21, 2002 10:18 AM
To: [EMAIL PROTECTED]
Subject: RE: Netscape vs. IE Discre
maybe you meant 'smart' as in the 'smart missile - really distructive'
sense?
joel
-Original Message-
From: Phil Fickas [mailto:[EMAIL PROTECTED]]
Sent: 21 May 2002 15:27
To: '[EMAIL PROTECTED]'
Subject: RE: Netscape vs. IE Discrepancy FIXED
Yea, I see that. I'm still hitting my self
Actually I was using an old, forgotten meaning of smart "To cause a sharp,
usually superficial, stinging pain." (without realizing it, of course :-)
http://www.dictionary.com/search?q=smart
1. To cause a sharp, usually superficial, stinging pain
2. To suffer acutely, as from mental distress, wo
Okay, can we stop this now? If you really want to test your code, try
Mozilla.
I've got a couple of questions. First, how do I untaint data when I want to
open a filehandle?
Secondly, I have this inside an if conditional inside a foreach loop
"$subject = "Sneak Preview Form Inquiry". It doesn't
On Tuesday, May 21, 2002, at 06:43 , David Gray wrote:
>> if (!($icname =~ /^[$allow]+$/)) {
[..]
> if($icname !~ /^[$allow]+$/) {
[..]
> }
personally I would have done the
unless ($icname =~ /^[$allow]+$/) {
# do ourstuff since $icname is not allowed
On Tuesday, May 21, 2002, at 05:58 , Felix Geerinckx wrote:
> on Tue, 21 May 2002 12:35:59 GMT, [EMAIL PROTECTED] (Bob
> Showalter) wrote:
>
>> This is dependent on the browser, and not the client OS. The
>> HTML standard would be controlling here, and it's pretty
>> vague if you look at the TEX
Hello all...'nuther goofy question
This bit of code...
open(outfile, ">".$pathToXML ) or die ("couldnt open xml file");
flock(outfile, 2);
print outfile $text;
close(outfile);
generates the following messages in my error_log
Unquoted string "outfile" may clash with future reserved word at
/va
> so I guess the question is - presume that it is either or
> and rip them all out before proceding anyway
IMHO I think one should presume that it is that way...Thats why we go to the
trouble to have standards isnt it? so that everyone doesnt have to go around
doing custom work for every
Hello,
A friend of mine has a task he wants to do daily, so I told him to check
into cron but he said he doesn't have it. His server is running RedHat 6.1
Cartman. I've never used cron before but I'm assuming that it is not
available to him from what he said. Is there an alternative to cron fo
24 matches
Mail list logo
