Thank you, Google, for making it oh so easy to have to list a dozen or so subdomains to enable maps.google.com to work through our firewall.
Thing is, Google, we shouldn't have to add tons of subdomains into our firewall just to get a single service (e.g. maps.google.com). maps.google.com should be it. Should be all we need to add to our firewall. This is my personal opinion. On Jan 8, 8:54 pm, Neddy <[email protected]> wrote: > Hi guys, > I have a hotspot system which has just been and refers to google maps > api to load maps/terrain and pinpoint hotspot locations... > > Basically i want to be able to allow all traffic to any google maps > services that the api uses (but block every other website on the > inet)... > > Does anyone have a list of what sub-domains:<port(s)> should be > allowed for google maps? > > At the moment i'm using: > > <code> > maps.google.com > mt0.google.com > mt1.google.com > mt2.google.com > mt3.google.com > mt4.google.com > mt5.google.com > kh0.google.com > kh1.google.com > kh2.google.com > kh3.google.com > kh4.google.com > kh5.google.com > local.google.com > </code> > > And it is still not working properly. > Cheers in advance. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
