Here is how it looks from our server:

# curl "http://ajax.googleapis.com/ajax/services/search/news?
v=1.0&rsz=large&q=bmw&hl=en&key=ABQIAAAA5BigVLONmmeStq-
mwWS6PxR45tWBl23wpUeuBr2PXy9wxmsLohQsHsJv5WRFoH_EzRd8vq9CWa2niQ" -H
"Referer: http://daymix.com/bmw/"; -v --interface eth0:2969
* About to connect() to ajax.googleapis.com port 80
*   Trying 74.125.127.95... Bind local address to 10.110.29.169
* SO_BINDTODEVICE eth0:2969 failed
* Local port: 46625
* connected
* Connected to ajax.googleapis.com (74.125.127.95) port 80
> GET 
> /ajax/services/search/news?v=1.0&rsz=large&q=bmw&hl=en&key=ABQIAAAA5BigVLONmmeStq-mwWS6PxR45tWBl23wpUeuBr2PXy9wxmsLohQsHsJv5WRFoH_EzRd8vq9CWa2niQ
>  HTTP/1.1
> User-Agent: curl/7.15.5 (x86_64-redhat-linux-gnu) libcurl/7.15.5 
> OpenSSL/0.9.8b zlib/1.2.3 libidn/0.6.5
> Host: ajax.googleapis.com
> Accept: */*
> Referer: http://daymix.com/bmw/
>

Has been sitting there open for 20 mins now
On Apr 16, 4:07 pm, Ryes <[email protected]> wrote:
> Yes, it is the same api key used on all servers.
> ABQIAAAA5BigVLONmmeStq-
> mwWS6PxR45tWBl23wpUeuBr2PXy9wxmsLohQsHsJv5WRFoH_EzRd8vq9CWa2niQ
>
> It should be registered for our domain too.
>
> Ryan
>
> On Apr 16, 9:30 am, Ben Lisbakken <[email protected]> wrote:
>
>
>
> > Ryan -
> > Are you sure you have the correct API key for your prod server?  Apologies
> > for asking, I just want to rule it out as a possibility.
>
> > -Ben
>
> > On Thu, Apr 16, 2009 at 9:06 AM, Ryes <[email protected]> wrote:
>
> > >http://pastebin.com/m2e7c6bcc
>
> > > Hrmm, good to know.  Ya, the code and url works fine on other ips and
> > > development servers, just the prod server doesn't work and only the
> > > news api, the web search and blog search work fine.  Does the news api
> > > route to a different server?
>
> > > Ryan
>
> > > On Apr 16, 8:35 am, Ben Lisbakken <[email protected]> wrote:
> > > > Hey Ryan --
> > > > Can you usehttp://pastebin.com/tocopy/pastethe exact URL's that you
> > > are
> > > > trying to access that are timing out?  We don't block IP's without
> > > > significant warning and in the rare case that we are forced to block
> > > someone
> > > > their requests will not timeout, but return an error message.  So
> > > something
> > > > else is going on here.
>
> > > > -Ben
>
> > > > On Wed, Apr 15, 2009 at 5:25 PM, Ryes <[email protected]> wrote:
>
> > > > > Oh, this is were we are using the API:
> > > > >http://daymix.com/American-Idol/
>
> > > > > but it is done server side with curl and so it doesn't work and
> > > > > doesn't show the google news block, but google web search and blog
> > > > > search work fine for some reason.
>
> > > > > Thank you,
> > > > > Ryan
>
> > > > > On Apr 14, 12:25 pm, Ben Lisbakken <[email protected]> wrote:
> > > > > > Hi Ryan -
>
> > > > > > Can you also provide a link to the script that is having these
> > > problems?
> > > > > > Looking at a live version that reproduces the bug will help us 
> > > > > > narrow
> > > > > down
> > > > > > the problem.
>
> > > > > > -Ben
>
> > > > > > On Apr 14, 2009 11:55 AM, "Ryes" <[email protected]> wrote:
>
> > > > > > I have this problem where the google news api timesout and doesn't
> > > > > > work on our production COLO, but the web and blog search works.  
> > > > > > Plus
> > > > > > on our other servers the news search works.
>
> > > > > > It seems maybe the ips on our prod are banned?  But only for news
> > > > > > search?  Anyway to figure out what the problem is on Google's side 
> > > > > > so
> > > > > > we can fix any problems?
>
> > > > > > Our api key is
> > > > > > ABQIAAAA5BigVLONmmeStq-
> > > > > > mwWS6PxR45tWBl23wpUeuBr2PXy9wxmsLohQsHsJv5WRFoH_EzRd8vq9CWa2niQ
>
> > > > > > Thank you,
> > > > > > Ryan

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google AJAX APIs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-AJAX-Search-API?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to