I am definitely using the Maps API and have no idea what the callback argument does. Specifically, I'm using the getLatLong() function.
Using FireBug, I've traced the error to this request made by getLatLong () which returns 400 Bad Request: http://maps.google.com/maps/geo?output=json&oe=utf-8&q=95%20Darling%20Ave%2C%20South%20Portland%2C%20MAINE%2C%20USA%2C%2004106&key=ABQIAAAAcJL-Tf_PkGgNrlpEBaSl7RQUIejMsNLPTvoc3Y2exiYiqDYTHxS2FuFaMIHoJLmRhaA3NctjAjieNQ&mapclient=jsapi&hl=en&callback=_xdc_._2g1mheg61 I've tried the getLocations() function and it also has the same issue. The URL of my site is: http://rrtexternalweb.wrightexpress.com/neo_ww/site_locator/list.action We did some load testing a few days ago so I wouldn't be shocked if my proxy was temporarily black listed. If that's the case it looks like the google geocoding server isn't automagically removing us from the black list like it should be. On Nov 5, 2:51 pm, Barry Hunter <[email protected]> wrote: > My guess is Google have noticed people abusing the geocoder and have > started to actively block certain requests. > > calls that use callback and dont originate from the Maps API itself > are a prime candidate for blocking > (because using callback yourself means you working outside of the API) > > And requests from behind a proxy are subject to extra scrutiny, so a > few legitimate requests are getting caught in the crossfire? > > 2009/11/4 AndyWins <[email protected]>: > > > I am also having the exact same problem. The geocoding URLs return > > 400 but when I remove &callback they work. The requests also work > > when I plug in outside of my proxy servers. > > > My issue mysteriously started within the past day or so. My mapping > > pages have been working great for the past 18 months or so (until now, > > that is). > > > On Nov 4, 11:58 am, Andrew Leach <[email protected]> wrote: > >> On Nov 4, 3:00 pm, Crazydj81 <[email protected]> wrote: > > >> > I went to the > >> > pagehttp://groups.google.com/group/google-maps-api/browse_thread/thread/b... > > >> > and it doesn't work either > > >> Given that you're also having difficulty with your own page in this > >> threadhttp://groups.google.com/group/google-maps-api/browse_thread/thread/6... > >> and no-one else is, it would appear to be something to do with the way > >> your network or client is sending the request or interpreting the > >> response. > > >> You may be able to investigate the response with Firebug, but if all > >> that is coming back is "invalid request" or something similar, then it > >> will be the request as received by the server which is suspect. That > >> may not resemble the request which leaves your browser. > > >> Andrew > > > -- > > > You received this message because you are subscribed to the Google Groups > > "Google Maps API" 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 > > athttp://groups.google.com/group/google-maps-api?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-maps-api?hl=en.
