From afc38aa121ae8bdb18c1912e269bc124622cfdb8 Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Fri, 26 Sep 2025 14:51:39 +0200 Subject: [PATCH 1/2] [GeoIP processor] Add clarification about using a reverse proxy endpoint --- docs/reference/ingest/processors/geoip.asciidoc | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/ingest/processors/geoip.asciidoc b/docs/reference/ingest/processors/geoip.asciidoc index 8246d881229e6..bf0fb80d2d152 100644 --- a/docs/reference/ingest/processors/geoip.asciidoc +++ b/docs/reference/ingest/processors/geoip.asciidoc @@ -343,15 +343,15 @@ GET /my_ip_locations/_search If you can't <> your IP geolocation databases from the Elastic endpoint, you have a few other options: -* <> +* <> * <> * <> [[use-proxy-geoip-endpoint]] -**Use a proxy endpoint** +**Use a reverse proxy endpoint** If you can't connect directly to the Elastic GeoIP endpoint, consider setting up -a secure proxy. You can then specify the proxy endpoint URL in the +a secure reverse proxy. You can then specify the reverse proxy endpoint URL in the <> setting of each node’s `elasticsearch.yml` file. From f53cbf0f8c18cfac8fa2b12d5933ae6629dbb6c4 Mon Sep 17 00:00:00 2001 From: Visha Angelova Date: Mon, 29 Sep 2025 11:33:25 +0200 Subject: [PATCH 2/2] Add clarifying note --- docs/reference/ingest/processors/geoip.asciidoc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/reference/ingest/processors/geoip.asciidoc b/docs/reference/ingest/processors/geoip.asciidoc index bf0fb80d2d152..bb42bcd175af3 100644 --- a/docs/reference/ingest/processors/geoip.asciidoc +++ b/docs/reference/ingest/processors/geoip.asciidoc @@ -355,6 +355,8 @@ a secure reverse proxy. You can then specify the reverse proxy endpoint URL in t <> setting of each node’s `elasticsearch.yml` file. +NOTE: True HTTP proxy support for GeoIP database downloads is not currently available in {es}. + In a strict setup the following domains may need to be added to the allowed domains list: