To finally assure you that's not %20: the same 610 error returns if you search for "London" for example (anything without spaces).
I don't see how the unminified source would help if it still comes down to a script request with a particular URL from the page on that particular server... You can use Goolge Chrome Dev Tools for debugging, creating script element in the source, setting its "src" to a certain Google Maps URL, doing document.body.appendChild(script) and then looking at the response in the resources tab. On Sep 22, 4:24 pm, Andrew Leach <[email protected]> wrote: > On 22 September 2011 14:18, Vladimir Agafonkin <[email protected]> wrote: > > > 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). > > In that case, please post an unminified version which can be debugged. > I remain convinced it's the %20 in the URL, because that's come up > before. -- 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.
