Ok so window.location.host comes back as dev.ahsinternet.com this is
the fake dns name I have created in my hosts file. This is the same
thing I generated my key for - they are exactly the same (unless the
http:// is counted when the key is generated....)

I am on displaying a map with a pointer on it to show where an
geographical residential address is (ie 1234 very happy drive, Beverly
hills, california, 90210) (I'm not sure if this counts as geocoding or
not). There could be a few pointers, but baby steps for now.

The problem is, I can't use the http://localhost as our server
framework specifically needs a realistic domain (its a portal server
framework, DNN, sitting on top of a server, and it reserves the
localhost term for some specialized logging services).

On Mar 18, 12:37 pm, Andrew Leach <[email protected]>
wrote:
> On Mar 18, 4:24 pm, [email protected] wrote:
>
> > From the link I gave you:
>
> > "If you want to test interaction with a server script..."
>
> I think that what D has done is to create a hosts file entry for a
> currently fictitious domain, saywww.myclientsnewsite.com, and
> generated a key for that. He can connect to his server using that
> "domain" name, because his hosts file directs the browser to his
> intranet IIS server.
>
> The question we need to ask is "What is window.location.host for your
> map page?" The key is checked against that value. Use that value to
> get the key.
>
> Or: use Remote Desktop to log into your IIS server and get to your map
> pages as localhost. You don't need a key for most map facilities on
> localhost (geocoding and driving directions do require a key)
>
> Andrew
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to