[32215] in Perl-Users-Digest
Perl-Users Digest, Issue: 3480 Volume: 11
daemon@ATHENA.MIT.EDU (Perl-Users Digest)
Tue Aug 23 18:09:32 2011
Date: Tue, 23 Aug 2011 15:09:07 -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 Tue, 23 Aug 2011 Volume: 11 Number: 3480
Today's topics:
Re: how do I create a hash from the list <tzz@lifelogs.com>
Illegal character in prototype for main hillgoogle@charter.net
Re: Illegal character in prototype for main <uri@StemSystems.com>
Re: Illegal character in prototype for main hillgoogle@charter.net
Re: Illegal character in prototype for main <rweikusat@mssgmbh.com>
Re: Illegal character in prototype for main hillgoogle@charter.net
Re: Illegal character in prototype for main <uri@StemSystems.com>
Re: Matching repetitions with /g <w.c.humann@arcor.de>
Posting Guidelines for comp.lang.perl.misc ($Revision: tadmc@seesig.invalid
Re: Script using LWP::UserAgent is sometimes failing wi <rweikusat@mssgmbh.com>
Script using LWP::UserAgent is sometimes failing with <davidmichaelkarr@gmail.com>
Re: Script using LWP::UserAgent is sometimes failing wi <davidmichaelkarr@gmail.com>
Re: Script using LWP::UserAgent is sometimes failing wi <davidmichaelkarr@gmail.com>
Digest Administrivia (Last modified: 6 Apr 01) (Perl-Users-Digest Admin)
----------------------------------------------------------------------
Date: Mon, 22 Aug 2011 13:04:20 -0500
From: Ted Zlatanov <tzz@lifelogs.com>
Subject: Re: how do I create a hash from the list
Message-Id: <8762lpjpaz.fsf@lifelogs.com>
On Fri, 19 Aug 2011 22:22:49 +0100 Rainer Weikusat <rweikusat@mssgmbh.com> wrote:
RW> Nene <rodbass63@gmail.com> writes:
>> I just used regular expressions to parse out an IP and port. Now how
>> do I create a hash from the list.
>>
>> Here is the regex I used:
>> perl -ne 'print "$1 $2\n" if /http:\/\/(\S+):(\d+)\/' {} \; | sort |
>> uniq
RW> '$hash{$1} = $2 if ...' ?
It's very unlikely the OP will want to do what you suggest, since he
shows two clearly identical IPs with different ports:
10.10.24.131 7002
10.10.24.142 7504
10.10.24.144 7506
10.10.24.150 7512
10.10.24.151 7413
10.10.24.151 7513
10.10.24.151 7613
Your way would lose the first two ports for 10.10.24.151.
I typically do this two ways, either
push @{$hash{$1}}, $2 if ... # keep an array of all the ports in order seen
or
$hash{$1}->{$2}++ # keep a hash of all the ports with a count of each
Of course the OP may need something else--it's not clear what, but I
would guess it's some variation of the two storage methods above.
Ted
------------------------------
Date: Tue, 23 Aug 2011 14:16:02 -0700 (PDT)
From: hillgoogle@charter.net
Subject: Illegal character in prototype for main
Message-Id: <c0602d7f-fc17-4249-939c-70518e5b1920@a27g2000yqc.googlegroups.com>
I have an issue in my perl and its due to my mis-underatanding of perl
sub.
In my main pgm i have this statement that is calling my mail program.
It works fine UNLESS i have a user like:
tim.o'leary@somecompany.com. When my user is just like
tim.oleary@somecompany.com then its fine. The error is "Illegal
character in prototype for main::SendMail : $,$,$ "
&SendMail($eml,$mail_text,$mail_sub);
sub SendMail($,$,$)
{
#who the email is being sent to
my $To = shift;
#the message body
my $mymsg = shift;
#the mail subject
my $mysubject = shift;
#From email address
my $from = "me\@somecompany.com";
my $msg = new MIME::Lite
To =>$To,
From =>$from,
Subject =>$mysubject,
Type =>'text/html',
Data =>$mymsg;
$msg->send;
}
Should I be putting these 3 vars in an array and then using that
array?
Thanks for your help. Mike
------------------------------
Date: Tue, 23 Aug 2011 17:21:53 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Illegal character in prototype for main
Message-Id: <8739grq0we.fsf@quad.sysarch.com>
>>>>> "h" == hillgoogle <hillgoogle@charter.net> writes:
h> In my main pgm i have this statement that is calling my mail program.
h> It works fine UNLESS i have a user like:
h> tim.o'leary@somecompany.com. When my user is just like
h> tim.oleary@somecompany.com then its fine. The error is "Illegal
h> character in prototype for main::SendMail : $,$,$ "
h> &SendMail($eml,$mail_text,$mail_sub);
don't use & for calling subs. actually it will also bypass the prototype
you are using
h> sub SendMail($,$,$)
and speaking of prototypes, they are not a good thing in general and
rarely needed. the , is not a prototype char and that is the bug you are
seeing. it should just be $$$. but since you bypass it by calling with &
you can see it is of little use here. just drop using them unless you
find a reason to use them.
h> {
h> #who the email is being sent to
useless comment.
h> my $To = shift;
h> #the message body
h> my $mymsg = shift;
h> #the mail subject
h> my $mysubject = shift;
much better to just assign to a list of vars:
my( $to, $msg, $subject ) = @_ ;
h> #From email address
h> my $from = "me\@somecompany.com";
use single quotes for literals without interpolation. and then you don't
need the \@
my $from = 'me@somecompany.com';
h> my $msg = new MIME::Lite
don't use indirect object calls. perldoc perlobj explains why. use a
direct call like this:
MIME::Lite->new(
uri
--
Uri Guttman -- uri AT perlhunter DOT com --- http://www.perlhunter.com --
------------ Perl Developer Recruiting and Placement Services -------------
----- Perl Code Review, Architecture, Development, Training, Support -------
------------------------------
Date: Tue, 23 Aug 2011 14:30:08 -0700 (PDT)
From: hillgoogle@charter.net
Subject: Re: Illegal character in prototype for main
Message-Id: <655bd4d2-6bbd-4f9d-a84a-d9efaccb9000@br5g2000vbb.googlegroups.com>
On Aug 23, 4:21=A0pm, "Uri Guttman" <u...@StemSystems.com> wrote:
> >>>>> "h" =3D=3D hillgoogle =A0<hillgoo...@charter.net> writes:
>
> =A0 h> In my main pgm i have this statement that is calling my mail progr=
am.
> =A0 h> It works fine UNLESS i have a user like:
> =A0 h> tim.o'le...@somecompany.com. When my user is just like
> =A0 h> tim.ole...@somecompany.com then its fine. The error is "Illegal
> =A0 h> character in prototype for main::SendMail : $,$,$ "
>
> =A0 h> &SendMail($eml,$mail_text,$mail_sub);
>
> don't use & for calling subs. actually it will also bypass the prototype
> you are using
>
> =A0 h> sub SendMail($,$,$)
>
> and speaking of prototypes, they are not a good thing in general and
> rarely needed. the , is not a prototype char and that is the bug you are
> seeing. it should just be $$$. but since you bypass it by calling with &
> you can see it is of little use here. just drop using them unless you
> find a reason to use them.
> =A0 h> {
> =A0 h> #who the email is being sent to
>
> useless comment.
>
> =A0 h> my $To =3D shift;
>
> =A0 h> #the message body
> =A0 h> my $mymsg =3D shift;
>
> =A0 h> #the mail subject
> =A0 h> my $mysubject =3D shift;
>
> much better to just assign to a list of vars:
>
> =A0 =A0 =A0 =A0 my( $to, $msg, $subject ) =3D @_ ;
>
> =A0 h> #From email address
> =A0 h> my $from =3D "me\@somecompany.com";
>
> use single quotes for literals without interpolation. and then you don't
> need the \@
>
> =A0 =A0 =A0 =A0 my $from =3D '...@somecompany.com';
>
> =A0 h> my $msg =3D new MIME::Lite
>
> don't use indirect object calls. perldoc perlobj explains why. use a
> direct call like this:
>
> =A0 =A0 =A0 =A0 MIME::Lite->new(
>
> uri
>
> --
> Uri Guttman =A0-- =A0uri AT perlhunter DOT com =A0--- =A0http://www.perlh=
unter.com--
> ------------ =A0Perl Developer Recruiting and Placement Services =A0-----=
--------
> ----- =A0Perl Code Review, Architecture, Development, Training, Support -=
------
Uri, so you are saying my code shold be as follows:
***************************************************************************=
***
SendMail($eml,$mail_text,$mail_sub);
sub SendMail($$$)
{
my ($To, $mymsg, $mysubject) =3D @_;
my $from =3D "me\@somecompany.com";
my $msg =3D MIME::Lite->new(
To =3D>$To,
From =3D>$from,
Subject =3D>$mysubject,
Type =3D>'text/html',
Data =3D>$mymsg);
$msg->send;
}
***************************************************************************=
***
Right?
:-) Mike
------------------------------
Date: Tue, 23 Aug 2011 22:41:52 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Illegal character in prototype for main
Message-Id: <87d3fvdcv3.fsf@sapphire.mobileactivedefense.com>
"Uri Guttman" <uri@StemSystems.com> writes:
>>>>>> "h" == hillgoogle <hillgoogle@charter.net> writes:
[...]
> h> &SendMail($eml,$mail_text,$mail_sub);
>
> don't use & for calling subs.
At least not when calling them with arguments. &something is useful in
subroutines performing some 'auxiliary task' and then 'forwarding' the
call to another routine: It means 'invoke something and use the
current @_ as argument list'. Semantically, this is (mostly)
equivalent to something(@_) except that it is shorter and the overhead
of creating a new @_ whose content is identical to the present @_ is
avoided.
------------------------------
Date: Tue, 23 Aug 2011 14:46:38 -0700 (PDT)
From: hillgoogle@charter.net
Subject: Re: Illegal character in prototype for main
Message-Id: <fe9c0ab3-643b-4a83-ac77-df9d377eef20@j5g2000vbk.googlegroups.com>
On Aug 23, 4:41=A0pm, Rainer Weikusat <rweiku...@mssgmbh.com> wrote:
> "Uri Guttman" <u...@StemSystems.com> writes:
> >>>>>> "h" =3D=3D hillgoogle =A0<hillgoo...@charter.net> writes:
>
> [...]
>
> > =A0 h> &SendMail($eml,$mail_text,$mail_sub);
>
> > don't use & for calling subs.
>
> At least not when calling them with arguments. &something is useful in
> subroutines performing some 'auxiliary task' and then 'forwarding' the
> call to another routine: It means 'invoke something and use the
> current @_ as argument list'. Semantically, this is (mostly)
> equivalent to something(@_) except that it is shorter and the overhead
> of creating a new @_ whose content is identical to the present @_ is
> avoided.
OK ... then it should be:
******************************************************************
&SendMail($eml,$mail_text,$mail_sub);
sub SendMail($$$)
{
my ($To, $mymsg, $mysubject) =3D @_;
my $from =3D 'me@somecompany.com';
my $msg =3D MIME::Lite->new(
To =3D>$To,
From =3D>$from,
Subject =3D>$mysubject,
Type =3D>'text/html',
Data =3D>$mymsg);
$msg->send;
}
******************************************************************
Better? TY Mike
------------------------------
Date: Tue, 23 Aug 2011 17:55:19 -0400
From: "Uri Guttman" <uri@StemSystems.com>
Subject: Re: Illegal character in prototype for main
Message-Id: <87obzfoks8.fsf@quad.sysarch.com>
>>>>> "h" == hillgoogle <hillgoogle@charter.net> writes:
h> Uri, so you are saying my code shold be as follows:
h> SendMail($eml,$mail_text,$mail_sub);
h> sub SendMail($$$)
drop the prototype.
sub SendMail {
and most put the opening { on the sub line.
h> {
h> my ($To, $mymsg, $mysubject) = @_;
don't mix upper/lower case names. also why the my prefix? they are
scoped with my so $msg and $subject are better names.
also indent code in the sub body.
h> my $from = "me\@somecompany.com";
you didn't change the quotes as i showed you.
h> my $msg = MIME::Lite->new(
h> To =>$To,
h> From =>$from,
h> Subject =>$mysubject,
h> Type =>'text/html',
h> Data =>$mymsg);
some white space helps there. also don't put the close ); on the data
line. it is hard to see and means you can't cut/paste that line or move
the close ) as easily.
h> $msg->send;
h> }
h> Right?
not completely but better. this is how i would do it. note ALL the
little changes like whitespace and name fixes.
send_mail( $eml, $mail_text, $mail_sub );
sub send_mail {
my( $to, $msg, $subject ) = @_;
my $from = 'me@somecompany.com';
my $msg = MIME::Lite->new(
To => $to,
From => $from,
Subject => $subject,
Type => 'text/html',
Data => $msg
);
$msg->send() ;
}
uri
--
Uri Guttman -- uri AT perlhunter DOT com --- http://www.perlhunter.com --
------------ Perl Developer Recruiting and Placement Services -------------
----- Perl Code Review, Architecture, Development, Training, Support -------
------------------------------
Date: Tue, 23 Aug 2011 06:30:40 -0700 (PDT)
From: Wolfram Humann <w.c.humann@arcor.de>
Subject: Re: Matching repetitions with /g
Message-Id: <1d343766-3f64-45a2-9009-2a6fcf39a188@a31g2000vbt.googlegroups.com>
Thanks for the replies. Sorry I couldn't comment for the last couple
of days. Yes, the reason for the anchor is indeed that I want to both
validate (that I don't capture arbitrary numbers from *some* line) and
capture. Perhaps it's indeed better to separate those tasks. I was
aware that the /g was pretty useless here, but I thought it served
well to show what I *wanted* to do.
Thanks again,
Wolfram
------------------------------
Date: Tue, 23 Aug 2011 02:18:50 -0500
From: tadmc@seesig.invalid
Subject: Posting Guidelines for comp.lang.perl.misc ($Revision: 1.9 $)
Message-Id: <nOGdnbHalrjHyc7TnZ2dnUVZ5t6dnZ2d@giganews.com>
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.9 $)
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.
The article at:
http://www.catb.org/~esr/faqs/smart-questions.html
describes how to get answers from technical people in general.
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://www.rehabitation.com/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 that they do
know and are being the "bad kind" of Lazy.
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_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
"top-posting", "Jeopardy" (because the answer comes before the
question), or "TOFU" (Text Over, Fullquote Under).
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 and many others on the comp.lang.perl.misc newsgroup.
--
Tad McClellan
email: perl -le "print scalar reverse qq/moc.liamg\100cm.j.dat/"
The above message is a Usenet post.
I don't recall having given anyone permission to use it on a Web site.
------------------------------
Date: Tue, 23 Aug 2011 18:03:49 +0100
From: Rainer Weikusat <rweikusat@mssgmbh.com>
Subject: Re: Script using LWP::UserAgent is sometimes failing with 500 error, although server reports 200
Message-Id: <87wre4oya2.fsf@sapphire.mobileactivedefense.com>
David Karr <davidmichaelkarr@gmail.com> writes:
> I have a Perl script that uses LWP::UserAgent to run a series of
> tests against a REST service running in an intranet. I configure it
> with a host and port to run its tests against. I've been using it
> for a while with no significant problems. Yesterday I started
> running tests against another server where my service was just
> deployed. This is a "final stage" environment, prior to production.
> My service is already deployed to production, this is just an
> additional release.
>
> For some reason, while running its tests against this new server,
> after getting numerous successful results back, the script is
> failing at no particular request with "500 read failed: Software
> caused connection abort".
http://www.google.com/#hl=en&cp=32&gs_id=2&xhr=t&q=Software+caused+connection+abort&pf=p&sclient=psy&site=&source=hp&pbx=1&oq=Software+caused+connection+abort&aq=0&aqi=g5&aql=&gs_sm=&gs_upl=&bav=on.2,or.r_gc.r_pw.&fp=c22dbf1ad5dc4c1f&biw=1598&bih=847
------------------------------
Date: Tue, 23 Aug 2011 08:56:43 -0700 (PDT)
From: David Karr <davidmichaelkarr@gmail.com>
Subject: Script using LWP::UserAgent is sometimes failing with 500 error, although server reports 200
Message-Id: <575d18fe-ee10-4a66-b9c5-a65a12a6632a@glegroupsg2000goo.googlegroups.com>
I have a Perl script that uses LWP::UserAgent to run a series of tests agai=
nst a REST service running in an intranet. I configure it with a host and =
port to run its tests against. I've been using it for a while with no sign=
ificant problems. Yesterday I started running tests against another server=
where my service was just deployed. This is a "final stage" environment, =
prior to production. My service is already deployed to production, this is=
just an additional release.
For some reason, while running its tests against this new server, after get=
ting numerous successful results back, the script is failing at no particul=
ar request with "500 read failed: Software caused connection abort". Even =
more curious, when I check the "access.log" on the server for that particul=
ar request, it reports a 200.
When I try to run that specific request manually, it always works fine. I =
also just checked with a QA tester that's using SoapUI to do similar testin=
g, and he hasn't seen any problems.
So, it seems like there's something in my Perl script that is causing some =
sort of a race condition that makes it think a request fails, when the serv=
er sees no problem.
I'll show the head of my Perl script, along with the excerpt of the code th=
at makes the request and checks for success.
-------------------
#!/usr/bin/perl -w
# -*- mode: Perl; -*-
use threads;
use threads::shared;
use Thread::Pool;
use Getopt::Long;
use LWP::UserAgent;
use HTTP::Request::Common qw(GET);
use XML::XPath;
use XML::XPath::XMLParser;
use Time::HiRes qw/gettimeofday/;
use List::MoreUtils qw(uniq);
...
sub sendGet($) {
my ($url) =3D @_;
if ($url =3D~ /\?/) {
foreach my $param (@opt_params) {
$url =3D $url . "&" . $param;
}
}
else {
$url =3D $url . "?";
foreach my $param (@opt_params) {
$url =3D $url . $param . "&";
}
}
print localtime() . ": url[$url]\n";
my $request =3D GET $url;
$request->header("X-Client-Code", "abc");
eval {
my $response =3D $ua->request($request);
if ($response->is_success) {
return $response->decoded_content;
}
else {
print "Call to url \"" . $url . "\" failed: " .
$response->status_line . "\n";
}
1;
} or do {
print "Call to url \"" . $url . "\" failed.\n";
}
}
----------------
When the failure occurs, it gets to the "Call to url ... failed:" line, wit=
h the status_line detail I provided earlier.
This server is running other applications that are being tested, although n=
ot heavily. I'm only one of two people that would be sending requests for =
this particular application right now, and the other one would only be test=
ing it lightly.
------------------------------
Date: Tue, 23 Aug 2011 08:58:19 -0700 (PDT)
From: David Karr <davidmichaelkarr@gmail.com>
Subject: Re: Script using LWP::UserAgent is sometimes failing with 500 error, although server reports 200
Message-Id: <2408e7f1-f5e8-4aec-8369-2a0b953ae181@glegroupsg2000goo.googlegroups.com>
Two details I should have provided:
I'm on Cygwin 1.5.25, and Perl 5.10.0.
------------------------------
Date: Tue, 23 Aug 2011 11:11:08 -0700 (PDT)
From: David Karr <davidmichaelkarr@gmail.com>
Subject: Re: Script using LWP::UserAgent is sometimes failing with 500 error, although server reports 200
Message-Id: <53753551-4e95-415a-bb38-e7c24b73fc1e@glegroupsg2000goo.googlegroups.com>
So far we've discovered that the URL I'm using is going through an F5 to th=
e web server, and if I change the test to go directly to the web server, it=
doesn't fail. Going through the F5 I get one random failure after it's be=
en running for a while (the script exits on the first failure). So far the=
network engineer hasn't found any obvious configuration details on the F5 =
that might cause this. Note that my requests are not using SSL.
It's pretty clear this isn't really a Perl problem, but something about how=
it works in my script is making the race condition surface.
------------------------------
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:
To submit articles to comp.lang.perl.announce, send your article to
clpa@perl.com.
Back issues are available via anonymous ftp from
ftp://cil-www.oce.orst.edu/pub/perl/old-digests.
#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 V11 Issue 3480
***************************************
