docs: remove ip tagging filter (#285)
This is not implemented. It can be added back for v2 only once it is implemented. Signed-off-by: Matt Klein <mklein@lyft.com>pull/289/head
parent
c6451f742b
commit
ba4bb89050
3 changed files with 0 additions and 49 deletions
@ -1,47 +0,0 @@ |
|||||||
.. _config_http_filters_ip_tagging: |
|
||||||
|
|
||||||
Ip tagging filter |
|
||||||
==================== |
|
||||||
|
|
||||||
This is an HTTP filter which enables Envoy to tag requests with extra information such as location, cloud source, and any |
|
||||||
extra data. This is useful to prevent against DDoS. |
|
||||||
|
|
||||||
**Note**: this filter is under active development, and currently does not perform any tagging on requests. In other |
|
||||||
words, installing this filter is a no-op in the filter chain. |
|
||||||
|
|
||||||
.. code-block:: json |
|
||||||
|
|
||||||
{ |
|
||||||
"name": "ip_tagging", |
|
||||||
"config": { |
|
||||||
"request_type": "...", |
|
||||||
"ip_tags": [] |
|
||||||
} |
|
||||||
} |
|
||||||
|
|
||||||
request_type |
|
||||||
*(optional, string)* The type of requests the filter should apply to. The supported |
|
||||||
types are *internal*, *external* or *both*. A request is considered internal if |
|
||||||
:ref:`x-envoy-internal<config_http_conn_man_headers_x-envoy-internal>` is set to true. If |
|
||||||
:ref:`x-envoy-internal<config_http_conn_man_headers_x-envoy-internal>` is not set or false, a |
|
||||||
request is considered external. The filter defaults to *both*, and it will apply to all request |
|
||||||
types. |
|
||||||
|
|
||||||
ip_tags: |
|
||||||
*(optional, array)* Specifies the list of ip tags to set for a request. |
|
||||||
|
|
||||||
Ip tags |
|
||||||
------- |
|
||||||
.. code-block:: json |
|
||||||
|
|
||||||
{ |
|
||||||
"ip_tag_name": "...", |
|
||||||
"ip_list": [] |
|
||||||
} |
|
||||||
|
|
||||||
ip_tag_name: |
|
||||||
*(required, string)* Specifies the ip tag name to apply. |
|
||||||
|
|
||||||
ip_list: |
|
||||||
*(required, list of strings)* A list of IP address and subnet masks that will be tagged with the ``ip_tag_name``. Both |
|
||||||
IPv4 and IPv6 CIDR addresses are allowed here. |
|
Loading…
Reference in new issue