Re: Scrapper outputing error -w

It would seem to me that the difference is that

$content = get('http://example.com/$device');
[download]

fails (or rather, returns undef) while

$content = get('http://example.com/test.html');
[download]

works. Maybe consider looking closer into what you actually get, and what is in $device and whether the request works from elsewhere.

Comment on Re: Scrapper outputing error -w Select or Download Code

Replies are listed 'Best First'.
Re^2: Scrapper outputing error -w by parkprimus (Sexton) on Apr 11, 2011 at 13:54 UTC
I definitely considered that and would only turn the perlmonks when all else fails. The output of $devices is as expected, I threw in a print statement to verify.	[reply]
Re^3: Scrapper outputing error -w by Corion (Patriarch) on Apr 11, 2011 at 13:57 UTC
You don't show us at all what path your data takes from `get(...)` until it gets to `HTML::PullParser`, where you get a warning (or two). What steps have you taken to confirm that you get the data you expect, and that you pass on the proper data down to HTML::PullParser in both cases? Please help us to help you better by posting a self-contained small program that exhibits the same failure. That way, we can more easily replicate your situation instead of taking guesses.	[reply] [d/l] [select]