Hey! Thanks! Tomorrow i'll test this solution. I've tested only in firefox, and the window.location.host brings me the www.srparticapações.com.br version. when register the key, the google says: "http://www.srparticipa%c3%a7%c3%b5es.com.br";. Will that "%c3%a7%c3%b5" be a problem to google API check against www.srpartipações.com.br?
PS: the participações.com.br is only a example name that i've used here, i can't post the real name that i'm using because the site is under construction, and my client don't want to, sorry. On Sep 20, 7:52 am, Mike Williams <[EMAIL PROTECTED]> wrote: > What's supposed to happen is that your browser converts characters that > are illegal in domain names into punycode (that's the weird xn-- stuff). > The problem is that most browsers return the punycode in > window.location.host, and some browsers (notably Firefox) convert it > back into accented characters. > > Your API key must agree with what the API sees in window.location.host > > That means that you have to register both versions of the key and switch > between them. > > See:http://mapki.com/wiki/Punycode > > However, there doesn't seem to be a webserver atwww.participações.com.br at > the moment. > > --http://econym.org.uk/gmap > The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
