You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafficserver.apache.org by "Peter Chou (JIRA)" <ji...@apache.org> on 2016/04/14 21:50:25 UTC
[jira] [Created] (TS-4353) Support multiple/custom GeoIP databases.
Peter Chou created TS-4353:
------------------------------
Summary: Support multiple/custom GeoIP databases.
Key: TS-4353
URL: https://issues.apache.org/jira/browse/TS-4353
Project: Traffic Server
Issue Type: Improvement
Components: Plugins
Reporter: Peter Chou
We have an internally developed plugin that we worked on based on suggestions from Shu Kit Chan. This plugin is a global/remap plugin that allows you to specify multiple IPv4 country databases in the global plugin.config file (important for multiple customers on an ATS instance). Each DB is assigned a tag string, e.g., --tag=foo --file=path-to-foo-file --tag=bar --file=path-to-bar-file.
In the remap context, the plugin will look-up the country code of the client IP and place it into an ATS internal header for down-chain plugins (such as tslua) to use. The selector for controlling which DB to use for the look-up for each remap rule is @pparam=foo.
I understand that GeoIP enhancements have recently been added to header_rewrite which can perform header changes based on GeoIP information. Would there be some value in adding the multiple/custom-DB feature to header_rewrite or possibly establishing a generic GeoIP helper plugin that handles the DB management for other plugins?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)