[
https://issues.apache.org/jira/browse/TS-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15255289#comment-15255289
]
James Peach commented on TS-4353:
---------------------------------
Can we come up with a plan to consolidate the geoip features? I'd like to avoid
a proliferation of slightly different ways to do geoip.
> 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
> Assignee: Kit Chan
> Fix For: sometime
>
>
> 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)
