4 ms·

Yeah, they are accessing the API via (view source): http://maps.google.com/maps/api/js?v=3.6&sensor=false&language=en&region=US&client=gme-volkswagenag http://m

by jyap 14y ago

Yeah, they are accessing the API via (view source): http://maps.google.com/maps/api/js?v=3.6&sensor=false&language=en&region=US&client=gme-volkswagenag http://maps.google.com/maps/api/js?v=3.6&sensor=false&#3... So the client ID is "gme-volkswagenag"... Which is a business client ID for the Google Maps API. So the error message FAQ points to: https://developers.google.com/maps/documentation/business/guide#URLs https://developers.google.com/maps/documentation/business/gu... So this client ID somehow is not valid for the URL (makes sense otherwise anybody could use VW's client ID). Perhaps they tested with something more restrictive like beta.vw.com. Seems like VW just needs to modify their authorized URLs for that client ID in their admin console. My opinion is that this Hacker News article title is wrong and misleading.

HaloZero 14y ago
That error message is exactly what you've mentioned. Basically the key that they are using for access has a whitelist of sites it is allowed to work on, they must have forgotten to include the production url to their key. It's a pretty quick fix on their side, somebody who owns that account just needs to add the url. Of course, finding out who owns the account who owns the key might be difficult at VW.