From 0c84591afe693256fc0631d4a89ccd1ee3ef6a78 Mon Sep 17 00:00:00 2001 From: Eric Leblond Date: Thu, 1 Aug 2019 09:49:17 +0200 Subject: [PATCH] doc: use a table to list direction filter in geoip --- doc/userguide/rules/header-keywords.rst | 16 ++++++++++------ 1 file changed, 10 insertions(+), 6 deletions(-) diff --git a/doc/userguide/rules/header-keywords.rst b/doc/userguide/rules/header-keywords.rst index d516fa2152..0a51d050f9 100644 --- a/doc/userguide/rules/header-keywords.rst +++ b/doc/userguide/rules/header-keywords.rst @@ -149,12 +149,16 @@ The syntax of geoip:: geoip: any,CN,IR; So, you can see you can use the following to make clear on which -direction you would like to match:: - - both: both directions have to match with the given geoip (geopip's) - any: one of the directions have to match with the given geoip ('s). - dest: if the destination matches with the given geoip. - src: the source matches with the given geoip. +direction you would like to match + +====== ============================================================= +Option Description +====== ============================================================= +both Both directions have to match with the given geoip (geopip's) +any One of the directions have to match with the given geoip ('s). +dest If the destination matches with the given geoip. +src The source matches with the given geoip. +====== ============================================================= The keyword only supports IPv4. As it uses the GeoIP2 API of MaxMind, libmaxminddb must be compiled in. You must download and install the -- 2.47.2