Re: Net::Google 502 Bad gateway errors
- From: "Ben Bullock" <benkasminbullock@xxxxxxxxx>
- Date: Sun, 21 May 2006 16:03:37 +0900
"Henry McGuinness" <henry.mcguinness@xxxxxxxxxxxxxx> wrote in message news:e4k6m1$lcf$1@xxxxxxxxxxxxxxxx
"Ben Bullock" <benkasminbullock@xxxxxxxxx> wrote in message news:e4jddl$h67$1@xxxxxxxxxxxxxxxxxxx"Henry McGuinness" <henry.mcguinness@xxxxxxxxxxxxxx> wrote in message news:e4hbvp$le9$1@xxxxxxxxxxxxxxxx
Believe it or not the solution is probably: leave it a couple of minutes and try again a few times. It does work, but sometimes rather sporadically. I found the Yahoo api stuff much more reliable. have a look at that: http://developer.yahoo.com/
OK, but what about just putting a search URL together then grabbing the page via libwww and parsing it using regular expressions though? That works almost every time, I never get any 502 errors, and the results are virtually instant. I can't see why I would want to use this Net::Google thing in the first place.
Maybe, but watch google's terms of service on this. They don't like "automated queries" and are not specific about all the types of query this includes: http://www.google.co.uk/intl/en/terms_of_service.html
I'm guessing that would be more directed at people like scroogle (http://www.scroogle.org/) than someone like me, who's unlikely to download more than 100 pages a day.
.
- References:
- Net::Google 502 Bad gateway errors
- From: Ben Bullock
- Re: Net::Google 502 Bad gateway errors
- From: Henry McGuinness
- Re: Net::Google 502 Bad gateway errors
- From: Ben Bullock
- Re: Net::Google 502 Bad gateway errors
- From: Henry McGuinness
- Net::Google 502 Bad gateway errors
- Prev by Date: Re: New module name? Pod::Pdf2
- Next by Date: Re: New module name? Pod::Pdf2
- Previous by thread: Re: Net::Google 502 Bad gateway errors
- Next by thread: Re: Net::Google 502 Bad gateway errors
- Index(es):