I discovered this problem earlier today. If you rearrange your URL so that "callback" is the LAST parameter, it will work. This seems like a bug on Google's end; the order of key/value pairs in a query string shouldn't make one whit of difference.
Adam http://adamschneider.net/ http://www.gpsvisualizer.com/ On Oct 30, 12:40 pm, Hugo <[email protected]> wrote: > As of yesterday a JSONP call to get reverse-geolocation data worked > just fine - no longer seems to be the case today. > > If you paste this link (w/ jsonpcallbackarguments) in your browser > it will return a 400 "Bad request" > > http://maps.google.com/maps/geo?callback=jsonp1256888593627&_=1256888... > > If you take out thecallbackarguments, leaving the rest of the URL > unchanged, all is good (200 http code, json data returned) > > http://maps.google.com/maps/geo?q=37.758199,-122.394628&key=ABQIAAAA-... > > Have jsonp calls been banned? That would seem...surprising... --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
