IP Tagging filter config

IP tagging data will be stored in the envoy config as a part of the HTTP Filter config. It is installed as a part of the HTTP Connection Manager filter chain.

{
  "type": "decoder",
  "name": "ip_tagging",
  "config": {
    // (optional, string) The type of requests the filter should apply to. External, internal 
    // Or both.
    "request_type": "...",
    // (optional, array) Specifies the list of ip tags to set for a request.
    "ip_tags": [
      {
        // (required, string) Specifies the ip tag name.
        "ip_tag_name": "...",
         // (required, list of strings) A list of IP address and subnet masks that will be
         // tagged with the ip_tag_name.
        "ip_list": []
      },
    	...
    ]
  }

HTTP IP Tagging filter

Maintain the IP Tags

When the IP Tagging filter is loaded, a level compressed trie(LC-trie) will be used to maintain the IP addresses and the associated tags. I will use these links for reference: http://www.drdobbs.com/cpp/fast-ip-routing-with-lc-tries/184410638 and
https://raminaji.wordpress.com/lc-trie/

Internals of the filter

When invoked, the trusted address from XFF will be used as the search key in the LC-trie.
The tags will be stored in a requests in the header x-envoy-ip-tags as a comma delimited list.

Note: All applicable tags will be appended to x-envoy-ip-tags.

IP tagging filter #1001

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions