500 Errors That Work

• Messages sorted by: [ date ][ thread ][ subject ][ author ]
• Next message: Mike Sheldrake: "RE: 500 Errors That Work"
• Previous message: Byron Brummer: "Re: Memory leak in LWP is not cured with perl's malloc()"

Hi,

I'm using LWP::UserAgent to test a series of ftp/http links with a
combination of LWP::UserAgent (to pull the list on links) with
LWP::Parallel::UserAgent (to do HEAD to check if the links work or not).

Ex: LWP::UserAgent pulls in the html file and grabs all the links found,
then passes it to a new object, (Parallel UA) to do the head requests

Now, I've encountered 2 critical problems:
1- Occassionally (mostly FTP sites), I get a 500 response code message, but
the actual link works fine (very bizarre!).
2- Long response requests will not timeout. I know this has been a problem
for many users, but the problem originates with LWP and not with the
Parallel UA. The author of PUA has been very helpful although none of the
patches or suggestions have worked to date. Has anyone been able to fix
either of these problems?

Thanks everyone.
PS: Marc, you've been a great help :)

Charles

Charles Michael
Web Automation Co-op
GO-DSP, A Texas Instruments Company
tel. 416-599-6868 ext. 240

• Next message: Mike Sheldrake: "RE: 500 Errors That Work"
• Previous message: Byron Brummer: "Re: Memory leak in LWP is not cured with perl's malloc()"