On Sep 17, 1:58 pm, marcelo <[EMAIL PROTECTED]> wrote: > > Are they really assigning private, (not public), IP addresses to their > subscribers? Unbelievable! > Exploiting people's ignorance must be part of their business model.
That's the case with a lot of companies -- some of what the blogosphere says is quite unreal [let the reader understand] AOL has a peculiar setup with IP addresses. There's a global pool which is all geolocated in Virginia. But I don't believe they are assigned a private address. Perhaps they are and all their proxies are located in Virginia. My Orange phone, though, has a "172" IP address and connects through a NetCache proxy at 193.35.132.151 which presents that IP address to the outside world. Not that I expect there will be all that many geocoding requests via phone browsers. Well-behaved proxies will give the X-FORWARDED-FOR header and Google might use that. Certainly where I've implemented an IP-checking routine to locate users, I check that header first and only discount it if it indicates a private address -- when I use the presented IP address. Google will need to use it rather than discount it if they're implementing a per-client rate check. If a proxy is badly-behaved and doesn't use that header, all bets are off, of course! 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 -~----------~----~----~----~------~----~------~--~---
