On Jun 12, 9:54 pm, Steve Lambert <[email protected]> wrote: > You can prove this by downloading one of the sample files that someone > else has posted and that includes their key...should work fine on your > local machine, but won't work if you upload it to your public server.
I know that someone else's key won't work on my public server. The API passes the referer header and the key to Google, and if they don't match, the key fails. I know that I can use any key for a page which has a file:// url, and that's good for tiles, geocoding and directions. For tiles, the API doesn't check the key for file:// urls, and for geocoding and directions, Google's servers don't get given a referer header to check the key against. With http://localhost, the tiles are served fine because localhost skips the key check for map tiles. I don't have an http://localhost server, so I can't prove that the geocoding and directions servers ignore a referer of localhost when they check the key. If you can prove that, please do. It certainly used to be the case that localhost needed a key for geocoding and directions to work. That may no longer be so. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
