Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

Unless there are objections, I will be merging this PR (#1866) in the near future. Please speak up now if you have any concerns. -- Thanks, Jeff On Mon, Feb 19, 2018 at 10:24 AM, Rivas, Jesse wrote: > Nir, > > I'm not familiar with the behavior of other geo DBs

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

If there are no objections to the proposed enhancement for a MaxMind override location on a per country, per CDN basis, then I will move forward with the changes and work with a committer to get the PR merged. -Jesse On 2/15/18, 8:37 AM, "Eric Friedrich (efriedri)" wrote:

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

Sounds great, thanks! > On Feb 15, 2018, at 10:33 AM, Rivas, Jesse wrote: > > Eric, > > We can determine a response from MaxMind is a default location when the > following conditions are met: the country code is populated, the city is > null, the postal code is null,

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

Eric, We can determine a response from MaxMind is a default location when the following conditions are met: the country code is populated, the city is null, the postal code is null, and the subdivisions list is empty. If these conditions are met, we check for an instance of

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

How does the suggested fix know when maxmind is returning a “default location” versus an actual location? Hopefully the solution is applicable to CDNs which are spread across multiple countries and geographies? —Eric > On Feb 13, 2018, at 1:34 PM, Rawlin Peters

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

I need to get better understanding of the DNS infra-structure to be able to verify this assumption. I assumed TR localization feature already solved the problem of getting to the right router, and from there it is in our hands ... Nir On Tue, Feb 13, 2018 at 11:39 PM, Rawlin Peters

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

Nir, You bring up a good point. If we can make the assumption that requests coming to a specific Traffic Router are actually somewhat local to that Traffic Router, we might be able to localize those "country-localized" clients to a cachegroup close to that particular Traffic Router. That would

Re: Traffic Router Enhancement - Default Maxmind Geolocation Override

Above I mentioned that the parameter 'maxmind.default.override' supports multiple entries so that there can be override coordinates for more than one country. To be more specific, the user can add multiple parameters using the same key to create multiple entries. Jesse On 2/13/18, 10:51 AM,