[23389] in Perl-Users-Digest
Perl-Users Digest, Issue: 5608 Volume: 10
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Fri Oct 3 09:05:41 2003
Date: Fri, 3 Oct 2003 06:05:06 -0700 (PDT)
From: Perl-Users Digest <Perl-Users-Request@ruby.OCE.ORST.EDU>
To: Perl-Users@ruby.OCE.ORST.EDU (Perl-Users Digest)
Perl-Users Digest Fri, 3 Oct 2003 Volume: 10 Number: 5608
Today's topics:
Re: DBD::Pg and bind_param <pilsl_usenet@goldfisch.at>
Re: DBI <tore@aursand.no>
Re: hashes <tore@aursand.no>
Re: javascript in HTML ... not running on some browsers <kaspREMOVE_CAPS@epatra.com>
Re: Perl CGI executing command line functions (Phil Meyer)
Re: Perl CGI executing command line functions <kuujinbo@hotmail.com>
Re: Perl CGI executing command line functions <flavell@ph.gla.ac.uk>
Re: Perl CGI executing command line functions <kuujinbo@hotmail.com>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@augustmail.com
Re: regex for URL in a log file <tzz@lifelogs.com>
Send two documents to browser? <REMOVEXtwoheadsX@tiscaliX.co.uk>
Re: Thanks news@roaima.freeserve.co.uk
Unexplained Multiple Lauches of Script with NetBackup . <jandk1@nospanners.comcast.net>
Re: <bwalton@rochester.rr.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Fri, 3 Oct 2003 13:20:56 +0200
From: peter pilsl <pilsl_usenet@goldfisch.at>
Subject: Re: DBD::Pg and bind_param
Message-Id: <3f7d5bd8@e-post.inode.at>
Chris Schadl wrote:
>
> chris@eclair:~/src/perl/sql$ ./mp3-insert.pl /export/mp3/mp3-X/Pixies\ -\
> Trompe\ Le\ Monde/ ...
> DBD::Pg::st execute failed: ERROR: Function 'insert_mp3(unknown, int4,
> int4, int4, int4, unknown, unknown, int4, unknown, unknown, unknown,
> unknown, unknown)' does not exist at ./mp3-insert.pl line 129.
> DBD::Pg::st execute failed: ERROR: Function 'insert_mp3(unknown, int4,
> int4, int4, int4, unknown, unknown, int4, unknown, unknown, unknown,
> unknown, unknown)' does not exist at ./mp3-insert.pl line 129.
>
> This is exactly the same error that I would recieve if I had simply called
> $sth->execute() with the given variables as arguments rather than passing
> them implicitly with bind_param. Does anyone know what I'm doing wrong?
>
Its really impossible to me to read all your script, cause its ways too
long. But to me it seems as if you didnt define the function insert_mp3
proper. (as the error says : "function ... does not exist"). So it looks
merely as a sql-problem than a perl- or DBD-problem.
As you say : if the error is the same if using bind or if not using bind,
it looks like the error has not to do with bind :)
If you want to test the bind_param-thing just create a small and simple
test-scenario that you can post here.
best,
peter
--
peter pilsl
pilsl_usenet@goldfisch.at
http://www.goldfisch.at
------------------------------
Date: Fri, 03 Oct 2003 11:24:30 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: DBI
Message-Id: <pan.2003.10.03.08.56.38.412227@aursand.no>
On Thu, 02 Oct 2003 21:11:17 +0000, Michael Budash wrote:
>>> also, the 'replace' query can be very useful:
>> Isn't that _very_ MySQL specific?
> not sure, quite possibly, but the o.p. did say:
> [...]
No matter what the OP said; My general advice is to _always_ avoid using
proprietary solutions. At least _try_ to avoid using them. Some day you
might end up rewriting your whole application because some retard thinks
that Oracle is a better database then MySQL. :-)
--
Tore Aursand <tore@aursand.no>
------------------------------
Date: Fri, 03 Oct 2003 11:24:29 +0200
From: Tore Aursand <tore@aursand.no>
Subject: Re: hashes
Message-Id: <pan.2003.10.03.08.54.35.622666@aursand.no>
On Thu, 02 Oct 2003 16:48:44 -0700, John Carroll wrote:
> $cgi = CGI->new ();
> $file_password = "testing";
> $password = $cgi->param ("Password");
You really should 'use strict', too;
my $cgi = CGI->new();
my $file_password = 'testing';
my $password = $cgi->param( 'Password' ) || '';
> print "file password: |$file_password|\n";
> print "password: |$password|\n";
> print $cgi->param('Password');
> print "\n";
> print "$cgi->param('Password')";
> print "\n";
Watch out for double quotes and what they do; They'll try to interpolate
what's inside them. I prefer to write things like this (thus making use
of the syntax highlighting in my editor);
print 'file password: |' . $file_password . '|' . "\n";
...
print $cgi->param( 'Password' ) . "\n";
Also remember that you can have a look at all the parameters:
my @params = $cgi->param();
foreach my $param ( @params ) {
print $param . ' = |' . $cgi->param( $param ) . '|' . "\n";
}
Nice for debugging etc.
--
Tore Aursand <tore@aursand.no>
------------------------------
Date: Fri, 3 Oct 2003 13:54:44 +0530
From: "Kasp" <kaspREMOVE_CAPS@epatra.com>
Subject: Re: javascript in HTML ... not running on some browsers
Message-Id: <bljbog$70e$1@newsreader.mailgate.org>
> Can someone tell me whats the problem ? And how can i solve it.
By posting your question in a Javascript or HTML related newsgroup.
--
"Accept that some days you are the pigeon and some days the statue."
"A pat on the back is only a few inches from a kick in the butt." - Dilbert.
------------------------------
Date: 3 Oct 2003 08:36:45 GMT
From: x0pmeyer@ti.com (Phil Meyer)
Subject: Re: Perl CGI executing command line functions
Message-Id: <bljcet$i4a$1@home.itg.ti.com>
In article <3eb8c8ea.0310020525.374773b9@posting.google.com>,
kvetchv@yahoo.com (Nick) writes:
> Thanks guys.
>
> tadmc@augustmail.com (Tad McClellan) wrote in message
>> You should learn Perl itself first, before moving on to a
>> complicated application area such as CGI programs.
>
> sounds like a fine idea and I intend to do this but I was hoping I
> could pick up enough to write this CGI program
This can all be done, and has been done safely before, and even presented
in this forum before. But the basics are:
By allowing an input field for a user to type into, you are subject to
stuff like this:
enter arguments to ls: -l ; cat /etc/passwd
See what I mean?
The best way to do this is with a pull down list, checkboxes, or something
similar. If you allow an input field, you have just allowed acces to the
system. If the list of things that they need to do is larger than the
scope of a list, then you need to provide them an account. At LEAST a
web account that they must log in with before using your tool. You would
also want your tool to log actions taken by userid.
Collecting process accounting for individual accounts is MUCH safer than
trying to figure out which IP was connected to the web server at the time
of the 'problem'.
Some years ago I did an application for the help desk that allowed them to
run common commands on any system in the data center by clicking on a web
page. It was used for first level system check before escalation. It
used secure shell from a trusted host, and some of the commands needed to
be run as root (vxdisk list, for example). The only way that this can be
done safely, is to define a finite set of commands that they will use, and
build forms that allow options by selection ONLY. Never an input field.
The cgi scripts that run these commands must have rigid checks of the fields
that they are passed. Even though they were hard coded in the forms, users
could figure out which cgi scripts are being called and try to pass them
commands directly.
Hope this helps.
------------------------------
Date: Fri, 03 Oct 2003 18:22:41 +0900
From: ko <kuujinbo@hotmail.com>
Subject: Re: Perl CGI executing command line functions
Message-Id: <bljf8i$bg1$1@pin3.tky.plala.or.jp>
Phil Meyer wrote:
[snip]
> This can all be done, and has been done safely before, and even presented
> in this forum before. But the basics are:
>
> By allowing an input field for a user to type into, you are subject to
> stuff like this:
>
> enter arguments to ls: -l ; cat /etc/passwd
>
> See what I mean?
>
> The best way to do this is with a pull down list, checkboxes, or something
> similar. If you allow an input field, you have just allowed acces to the
> system. If the list of things that they need to do is larger than the
> scope of a list, then you need to provide them an account. At LEAST a
> web account that they must log in with before using your tool. You would
> also want your tool to log actions taken by userid.
I have a question about whether an input field is any more secure than a
pull-down list/checkbox. Even though the form is hard-coded can't
aynyone submit pretty much anything they want, for example with LWP?
> Collecting process accounting for individual accounts is MUCH safer than
> trying to figure out which IP was connected to the web server at the time
> of the 'problem'.
>
> Some years ago I did an application for the help desk that allowed them to
> run common commands on any system in the data center by clicking on a web
> page. It was used for first level system check before escalation. It
> used secure shell from a trusted host, and some of the commands needed to
> be run as root (vxdisk list, for example). The only way that this can be
> done safely, is to define a finite set of commands that they will use, and
> build forms that allow options by selection ONLY. Never an input field.
>
> The cgi scripts that run these commands must have rigid checks of the fields
> that they are passed. Even though they were hard coded in the forms, users
> could figure out which cgi scripts are being called and try to pass them
> commands directly.
This is more what I thought you are supposed to do with CGI - rigidly
check all fields passed to the form - the person who builds the form
specifies a set of *acceptable* parameters, and anything that does not
fall in the defined set gets ignored, calls an error routine, etc. In
other words, all form element are equally not secure.
Please correct me if I am making any incorrect assumptions.
thanks - keith
------------------------------
Date: Fri, 3 Oct 2003 11:31:12 +0100
From: "Alan J. Flavell" <flavell@ph.gla.ac.uk>
Subject: Re: Perl CGI executing command line functions
Message-Id: <Pine.LNX.4.53.0310031127550.17252@ppepc56.ph.gla.ac.uk>
On Fri, 3 Oct 2003, ko wrote:
> I have a question about whether an input field is any more secure than a
> pull-down list/checkbox.
I have an answer, and it would be on-topic for
comp.infosystems.www.authoring.cgi because there's nothing
Perl-specific in it...
> Even though the form is hard-coded can't
> aynyone submit pretty much anything they want, for example with LWP?
Correct.
[...]
> Please correct me if I am making any incorrect assumptions.
About the appropriate group to post to, see above.
About the topic, see Lincoln Stein's web security FAQ.
But basically, as to content you seem to be on the right lines.
------------------------------
Date: Fri, 03 Oct 2003 20:20:41 +0900
From: ko <kuujinbo@hotmail.com>
Subject: Re: Perl CGI executing command line functions
Message-Id: <bljm5q$iop$1@pin3.tky.plala.or.jp>
Alan J. Flavell wrote:
> On Fri, 3 Oct 2003, ko wrote:
>
>
>>I have a question about whether an input field is any more secure than a
>>pull-down list/checkbox.
>
>
> I have an answer, and it would be on-topic for
> comp.infosystems.www.authoring.cgi because there's nothing
> Perl-specific in it...
>
[snip]
>
>>Please correct me if I am making any incorrect assumptions.
>
>
> About the appropriate group to post to, see above.
>
> About the topic, see Lincoln Stein's web security FAQ.
Thanks for the advice, I've already read the FAQ. I guess my overly
subtle (bad) attempt to give the OP a hint that he should check *all*
form element parameters should have been posed as statements rather than
questions.
And actually, a little over a year ago you were generous enough to help
me when I was writing my "First CGI script". Although I admit at least I
posted snippets of code :)
------------------------------
Date: Fri, 03 Oct 2003 02:23:00 -0500
From: tadmc@augustmail.com
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
Message-Id: <z8idnSuZ2qpJvuCiU-KYuA@august.net>
Outline
Before posting to comp.lang.perl.misc
Must
- Check the Perl Frequently Asked Questions (FAQ)
- Check the other standard Perl docs (*.pod)
Really Really Should
- Lurk for a while before posting
- Search a Usenet archive
If You Like
- Check Other Resources
Posting to comp.lang.perl.misc
Is there a better place to ask your question?
- Question should be about Perl, not about the application area
How to participate (post) in the clpmisc community
- Carefully choose the contents of your Subject header
- Use an effective followup style
- Speak Perl rather than English, when possible
- Ask perl to help you
- Do not re-type Perl code
- Provide enough information
- Do not provide too much information
- Do not post binaries, HTML, or MIME
Social faux pas to avoid
- Asking a Frequently Asked Question
- Asking a question easily answered by a cursory doc search
- Asking for emailed answers
- Beware of saying "doesn't work"
- Sending a "stealth" Cc copy
Be extra cautious when you get upset
- Count to ten before composing a followup when you are upset
- Count to ten after composing and before posting when you are upset
-----------------------------------------------------------------
Posting Guidelines for comp.lang.perl.misc ($Revision: 1.4 $)
This newsgroup, commonly called clpmisc, is a technical newsgroup
intended to be used for discussion of Perl related issues (except job
postings), whether it be comments or questions.
As you would expect, clpmisc discussions are usually very technical in
nature and there are conventions for conduct in technical newsgroups
going somewhat beyond those in non-technical newsgroups.
This article describes things that you should, and should not, do to
increase your chances of getting an answer to your Perl question. It is
available in POD, HTML and plain text formats at:
http://mail.augustmail.com/~tadmc/clpmisc.shtml
For more information about netiquette in general, see the "Netiquette
Guidelines" at:
http://andrew2.andrew.cmu.edu/rfc/rfc1855.html
A note to newsgroup "regulars":
Do not use these guidelines as a "license to flame" or other
meanness. It is possible that a poster is unaware of things
discussed here. Give them the benefit of the doubt, and just
help them learn how to post, rather than assume
A note about technical terms used here:
In this document, we use words like "must" and "should" as
they're used in technical conversation (such as you will
encounter in this newsgroup). When we say that you *must* do
something, we mean that if you don't do that something, then
it's unlikely that you will benefit much from this group.
We're not bossing you around; we're making the point without
lots of words.
Do *NOT* send email to the maintainer of these guidelines. It will be
discarded unread. The guidelines belong to the newsgroup so all
discussion should appear in the newsgroup. I am just the secretary that
writes down the consensus of the group.
Before posting to comp.lang.perl.misc
Must
This section describes things that you *must* do before posting to
clpmisc, in order to maximize your chances of getting meaningful replies
to your inquiry and to avoid getting flamed for being lazy and trying to
have others do your work.
The perl distribution includes documentation that is copied to your hard
drive when you install perl. Also installed is a program for looking
things up in that (and other) documentation named 'perldoc'.
You should either find out where the docs got installed on your system,
or use perldoc to find them for you. Type "perldoc perldoc" to learn how
to use perldoc itself. Type "perldoc perl" to start reading Perl's
standard documentation.
Check the Perl Frequently Asked Questions (FAQ)
Checking the FAQ before posting is required in Big 8 newsgroups in
general, there is nothing clpmisc-specific about this requirement.
You are expected to do this in nearly all newsgroups.
You can use the "-q" switch with perldoc to do a word search of the
questions in the Perl FAQs.
Check the other standard Perl docs (*.pod)
The perl distribution comes with much more documentation than is
available for most other newsgroups, so in clpmisc you should also
see if you can find an answer in the other (non-FAQ) standard docs
before posting.
It is *not* required, or even expected, that you actually *read* all of
Perl's standard docs, only that you spend a few minutes searching them
before posting.
Try doing a word-search in the standard docs for some words/phrases
taken from your problem statement or from your very carefully worded
"Subject:" header.
Really Really Should
This section describes things that you *really should* do before posting
to clpmisc.
Lurk for a while before posting
This is very important and expected in all newsgroups. Lurking means
to monitor a newsgroup for a period to become familiar with local
customs. Each newsgroup has specific customs and rituals. Knowing
these before you participate will help avoid embarrassing social
situations. Consider yourself to be a foreigner at first!
Search a Usenet archive
There are tens of thousands of Perl programmers. It is very likely
that your question has already been asked (and answered). See if you
can find where it has already been answered.
One such searchable archive is:
http://groups.google.com/advanced_group_search
If You Like
This section describes things that you *can* do before posting to
clpmisc.
Check Other Resources
You may want to check in books or on web sites to see if you can
find the answer to your question.
But you need to consider the source of such information: there are a
lot of very poor Perl books and web sites, and several good ones
too, of course.
Posting to comp.lang.perl.misc
There can be 200 messages in clpmisc in a single day. Nobody is going to
read every article. They must decide somehow which articles they are
going to read, and which they will skip.
Your post is in competition with 199 other posts. You need to "win"
before a person who can help you will even read your question.
These sections describe how you can help keep your article from being
one of the "skipped" ones.
Is there a better place to ask your question?
Question should be about Perl, not about the application area
It can be difficult to separate out where your problem really is,
but you should make a conscious effort to post to the most
applicable newsgroup. That is, after all, where you are the most
likely to find the people who know how to answer your question.
Being able to "partition" a problem is an essential skill for
effectively troubleshooting programming problems. If you don't get
that right, you end up looking for answers in the wrong places.
It should be understood that you may not know that the root of your
problem is not Perl-related (the two most frequent ones are CGI and
Operating System related), so off-topic postings will happen from
time to time. Be gracious when someone helps you find a better place
to ask your question by pointing you to a more applicable newsgroup.
How to participate (post) in the clpmisc community
Carefully choose the contents of your Subject header
You have 40 precious characters of Subject to win out and be one of
the posts that gets read. Don't waste them. Take care while
composing them, they are the key that opens the door to getting an
answer.
Spend them indicating what aspect of Perl others will find if they
should decide to read your article.
Do not spend them indicating "experience level" (guru, newbie...).
Do not spend them pleading (please read, urgent, help!...).
Do not spend them on non-Subjects (Perl question, one-word
Subject...)
For more information on choosing a Subject see "Choosing Good
Subject Lines":
http://www.cpan.org/authors/id/D/DM/DMR/subjects.post
Part of the beauty of newsgroup dynamics, is that you can contribute
to the community with your very first post! If your choice of
Subject leads a fellow Perler to find the thread you are starting,
then even asking a question helps us all.
Use an effective followup style
When composing a followup, quote only enough text to establish the
context for the comments that you will add. Always indicate who
wrote the quoted material. Never quote an entire article. Never
quote a .signature (unless that is what you are commenting on).
Intersperse your comments *following* each section of quoted text to
which they relate. Unappreciated followup styles are referred to as
"Jeopardy" (because the answer comes before the question), or
"TOFU".
Reversing the chronology of the dialog makes it much harder to
understand (some folks won't even read it if written in that style).
For more information on quoting style, see:
http://web.presby.edu/~nnqadmin/nnq/nquote.html
Speak Perl rather than English, when possible
Perl is much more precise than natural language. Saying it in Perl
instead will avoid misunderstanding your question or problem.
Do not say: I have variable with "foo\tbar" in it.
Instead say: I have $var = "foo\tbar", or I have $var = 'foo\tbar',
or I have $var = <DATA> (and show the data line).
Ask perl to help you
You can ask perl itself to help you find common programming mistakes
by doing two things: enable warnings (perldoc warnings) and enable
"strict"ures (perldoc strict).
You should not bother the hundreds/thousands of readers of the
newsgroup without first seeing if a machine can help you find your
problem. It is demeaning to be asked to do the work of a machine. It
will annoy the readers of your article.
You can look up any of the messages that perl might issue to find
out what the message means and how to resolve the potential mistake
(perldoc perldiag). If you would like perl to look them up for you,
you can put "use diagnostics;" near the top of your program.
Do not re-type Perl code
Use copy/paste or your editor's "import" function rather than
attempting to type in your code. If you make a typo you will get
followups about your typos instead of about the question you are
trying to get answered.
Provide enough information
If you do the things in this item, you will have an Extremely Good
chance of getting people to try and help you with your problem!
These features are a really big bonus toward your question winning
out over all of the other posts that you are competing with.
First make a short (less than 20-30 lines) and *complete* program
that illustrates the problem you are having. People should be able
to run your program by copy/pasting the code from your article. (You
will find that doing this step very often reveals your problem
directly. Leading to an answer much more quickly and reliably than
posting to Usenet.)
Describe *precisely* the input to your program. Also provide example
input data for your program. If you need to show file input, use the
__DATA__ token (perldata.pod) to provide the file contents inside of
your Perl program.
Show the output (including the verbatim text of any messages) of
your program.
Describe how you want the output to be different from what you are
getting.
If you have no idea at all of how to code up your situation, be sure
to at least describe the 2 things that you *do* know: input and
desired output.
Do not provide too much information
Do not just post your entire program for debugging. Most especially
do not post someone *else's* entire program.
Do not post binaries, HTML, or MIME
clpmisc is a text only newsgroup. If you have images or binaries
that explain your question, put them in a publically accessible
place (like a Web server) and provide a pointer to that location. If
you include code, cut and paste it directly in the message body.
Don't attach anything to the message. Don't post vcards or HTML.
Many people (and even some Usenet servers) will automatically filter
out such messages. Many people will not be able to easily read your
post. Plain text is something everyone can read.
Social faux pas to avoid
The first two below are symptoms of lots of FAQ asking here in clpmisc.
It happens so often that folks will assume that it is happening yet
again. If you have looked but not found, or found but didn't understand
the docs, say so in your article.
Asking a Frequently Asked Question
It should be understood that you may have missed the applicable FAQ
when you checked, which is not a big deal. But if the Frequently
Asked Question is worded similar to your question, folks will assume
that you did not look at all. Don't become indignant at pointers to
the FAQ, particularly if it solves your problem.
Asking a question easily answered by a cursory doc search
If folks think you have not even tried the obvious step of reading
the docs applicable to your problem, they are likely to become
annoyed.
If you are flamed for not checking when you *did* check, then just
shrug it off (and take the answer that you got).
Asking for emailed answers
Emailed answers benefit one person. Posted answers benefit the
entire community. If folks can take the time to answer your
question, then you can take the time to go get the answer in the
same place where you asked the question.
It is OK to ask for a *copy* of the answer to be emailed, but many
will ignore such requests anyway. If you munge your address, you
should never expect (or ask) to get email in response to a Usenet
post.
Ask the question here, get the answer here (maybe).
Beware of saying "doesn't work"
This is a "red flag" phrase. If you find yourself writing that,
pause and see if you can't describe what is not working without
saying "doesn't work". That is, describe how it is not what you
want.
Sending a "stealth" Cc copy
A "stealth Cc" is when you both email and post a reply without
indicating *in the body* that you are doing so.
Be extra cautious when you get upset
Count to ten before composing a followup when you are upset
This is recommended in all Usenet newsgroups. Here in clpmisc, most
flaming sub-threads are not about any feature of Perl at all! They
are most often for what was seen as a breach of netiquette. If you
have lurked for a bit, then you will know what is expected and won't
make such posts in the first place.
But if you get upset, wait a while before writing your followup. I
recommend waiting at least 30 minutes.
Count to ten after composing and before posting when you are upset
After you have written your followup, wait *another* 30 minutes
before committing yourself by posting it. You cannot take it back
once it has been said.
AUTHOR
Tad McClellan <tadmc@augustmail.com> and many others on the
comp.lang.perl.misc newsgroup.
------------------------------
Date: Fri, 03 Oct 2003 06:06:05 -0400
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: regex for URL in a log file
Message-Id: <4nr81ur5yq.fsf@lockgroove.bwh.harvard.edu>
--=-=-=
On Thu, 2 Oct 2003, darthlover@yahoo.com wrote:
> hail all,
> I am trying to write a regular expression to match a url in a
> text file. the test file looks like below under the ********* I
> would like to match all the urls a print them out...
> I think this is easy for most but a pain in the neck for me
This is what I use, it can take both URLs and files as parameters.
Starting point was provided by other c.l.p.misc posts. Comments
welcome.
Ted
--=-=-=
Content-Type: application/x-perl
Content-Disposition: attachment; filename=getlinks.pl
#!/usr/bin/perl -w
use LWP::UserAgent;
use HTML::LinkExtor;
use URI::URL;
use strict;
foreach my $url (@ARGV)
{
if (-e $url)
{
my $file = $url;
if ($file !~ m#^/#)
{
my $pwd = `pwd`;
chomp $pwd;
$url = "$pwd/$file"
}
$url = "file://$url";
print "Operating on file $file, actual URL $url\n";
}
my $ua = LWP::UserAgent->new;
# Set up a callback that collect image links
my @links = ();
sub callback
{
my($tag, %attr) = @_;
# return if $tag ne 'img'; # we only look closer at <img ...>
push(@links, values %attr);
}
# Make the parser. Unfortunately, we don't know the base yet
# (it might be diffent from $url)
my $p = HTML::LinkExtor->new(\&callback);
# Request document and parse it as it arrives
my $res = $ua->request(HTTP::Request->new(GET => $url),
sub {$p->parse($_[0])});
# Expand all URLs to absolute ones
my $base = $res->base;
@links = map { $_ = url($_, $base)->abs; } @links;
# Print them out
print join("\n", @links), "\n";
}
--=-=-=--
------------------------------
Date: Fri, 03 Oct 2003 09:46:37 +0100
From: Mark <REMOVEXtwoheadsX@tiscaliX.co.uk>
Subject: Send two documents to browser?
Message-Id: <gadqnvkd5rkb0vehgru1s3r7nhqlohi6io@4ax.com>
Hi All,
I have a commercial website search script which is slow in returning
its results. The consequence is that for a short period the screen is
white until the results are returned.
Is there a simple way to make the script return a temporary document
to the browser which is then replaced by the search results?
I tried making the script print some standard html code at the start
of the script and this seemed to do the trick but then a discovered
that my original document (which was simply a black background) was
not being replaced. The new document was being printed after the
first, resulting in the document headers being printed rather than
being interpreted by the browser.
Many thanks in advance for any suggestions.
Mark
------------------------------
Date: Fri, 3 Oct 2003 09:35:09 +0100
From: news@roaima.freeserve.co.uk
Subject: Re: Thanks
Message-Id: <tuov41-esj.ln1@news.roaima.co.uk>
Florian von Savigny <florian265@uboot.com> wrote:
> I have taken to setting and resetting $| before and after each such
> print statement, which may have been more work than Brian's proposal
> after all. But in any case, it has worked like a snap.
You may find it's easier - and more readable - just to set $| at the
beginning of the script or section. The tradeoff is buffering (efficiency)
vs no buffering (it works as you expect).
Chris
--
@s=split(//,"Je,\nhn ersloak rcet thuarP");$k=$l=@s;for(;$k;$k--){$i=($i+1)%$l
until$s[$i];$c=$s[$i];print$c;undef$s[$i];$i=($i+(ord$c))%$l}
------------------------------
Date: Fri, 3 Oct 2003 08:11:19 -0400
From: "Jay W" <jandk1@nospanners.comcast.net>
Subject: Unexplained Multiple Lauches of Script with NetBackup ... could it be PERL?
Message-Id: <8_2cnfo5-731-uCiXTWJig@comcast.com>
I have a PERL script that is executed by NetBackup "bpstart". From within
the script two different lines are launched depending on the Policy passed
to bpstart in %2. Only one of the two lines should be launched at any given
time.
The problem is that shortly after launching the script (about 5 minutes), a
second occurrance starts, then a 3rd, then a 4th .... up to 29 occurances in
some cases. Usually this scenario ends with a Dr Watson abort. The odd thing
is that I use about 7 command line parameters that are identical in each
launch, so a full command line is being "re-executed" :
function: Perl_dounwind
280363f1 b903010000 mov ecx,0x103
280363f6 7417 jz Perl_sv_compile_2op+0x6fa0
(2803ef0f)
*----> Stack Back Trace <----*
FramePtr ReturnAd Param#1 Param#2 Param#3 Param#4 Function Name
0140FD9C 2805D784 01B31308 015D41C4 28024499 015D41C4 !Perl_dounwind
0140FE24 280862DE 015D41C4 00000000 00000000 505C3A43 !Perl_runops_standard
0140FF3C 00401012 0000000C 015D24B0 015D2AF8 004010F9 !RunPerl
0140FFC0 77E9CA90 00000000 00000000 7FFDF000 C0000005 !<nosymbols>
0140FFF0 00000000 00401016 00000000 000000C8 00000100
kernel32!CreateProcessW
I guess, the questions are :
1. Has anyone else run into this?
2. Is there a syntax that may inadvertantly start another instance of the
command that was originally launched? (I'm 1st year PERL)
I'm trying to prove through debug code that it is NetBackup's fault and not
PERL
Env :
W2K AS - SP4
ActiveState PERL 5.8.1
------------------------------
Date: Sat, 19 Jul 2003 01:59:56 GMT
From: Bob Walton <bwalton@rochester.rr.com>
Subject: Re:
Message-Id: <3F18A600.3040306@rochester.rr.com>
Ron wrote:
> Tried this code get a server 500 error.
>
> Anyone know what's wrong with it?
>
> if $DayName eq "Select a Day" or $RouteName eq "Select A Route") {
(---^
> dienice("Please use the back button on your browser to fill out the Day
> & Route fields.");
> }
...
> Ron
...
--
Bob Walton
------------------------------
Date: 6 Apr 2001 21:33:47 GMT (Last modified)
From: Perl-Users-Request@ruby.oce.orst.edu (Perl-Users-Digest Admin)
Subject: Digest Administrivia (Last modified: 6 Apr 01)
Message-Id: <null>
Administrivia:
The Perl-Users Digest is a retransmission of the USENET newsgroup
comp.lang.perl.misc. For subscription or unsubscription requests, send
the single line:
subscribe perl-users
or:
unsubscribe perl-users
to almanac@ruby.oce.orst.edu.
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
To request back copies (available for a week or so), send your request
to almanac@ruby.oce.orst.edu with the command "send perl-users x.y",
where x is the volume number and y is the issue number.
For other requests pertaining to the digest, send mail to
perl-users-request@ruby.oce.orst.edu. Do not waste your time or mine
sending perl questions to the -request address, I don't have time to
answer them even if I did know the answer.
------------------------------
End of Perl-Users Digest V10 Issue 5608
***************************************
