You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficcontrol.apache.org by "Nir Sopher (JIRA)" <ji...@apache.org> on 2017/08/15 20:32:00 UTC

[jira] [Created] (TC-529) TRAFFIC_ROUTER default profile points to non existing geolocation DB endpoint

Nir Sopher created TC-529:
-----------------------------

             Summary: TRAFFIC_ROUTER default profile points to non existing geolocation DB endpoint
                 Key: TC-529
                 URL: https://issues.apache.org/jira/browse/TC-529
             Project: Traffic Control
          Issue Type: Improvement
          Components: Traffic Router
    Affects Versions: 2.1.0
            Reporter: Nir Sopher
            Priority: Minor


The "eolocation.polling.url" variable in the TRAFFIC_ROUTER default profile published at http://trafficcontrol.apache.org/downloads/profiles/2.0.x/default/TRAFFIC_ROUTER_PROFILE.traffic_ops is set to http://${toHostname}/MaxMind/auto/GeoIP2-City.mmdb.gz.

However, this path does not exists in my traffic ops.
However, the path  "routing/GeoLite2-City.mmdb.gz" does exists



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)