Doesn't help. And If I open the app locally and do the search in the search box which in turn does the request, it works. So it's not about escapement - the application logic is fine. The problem arises only after putting the page on the server (with domain for which the API key is registered).
On Sep 22, 4:09 pm, Andrew Leach <[email protected]> wrote: > On Sep 22, 2:03 pm, Vladimir Agafonkin <[email protected]> wrote: > > > Nope, since the URL works fine when you open it in the browser > > separately, and returns 610 ("bad key") error when you do the request > > from a page, it's not related to the request itself - only to the API > > key validation. > > > You can try registering the API key forhttp://10k.aneventapart.com > > domain yourself and you'll see that it's the same as the one in the > > URL I provided. So I'm pretty sure it's something on the Google side. > > Have you actually tried what I suggested? > > I reckon it's the presence of %20 in the URL which is upsetting the > processing Google does. Try rearranging the URL so that the key is > done first; or replace %20 with +. When you open the URL in the > browser, %20 is replaced with a real space, and Google doesn't get the > characters %20 so the problem doesn't arise. -- You received this message because you are subscribed to the Google Groups "Google Maps API V2" 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.
