From c90b277cb8b859aa452041a72d066cdc4c19338d Mon Sep 17 00:00:00 2001 From: Visha Angelova <91186315+vishaangelova@users.noreply.github.com> Date: Mon, 29 Sep 2025 12:20:33 +0200 Subject: [PATCH] [8.19][DOCS] GeoIP processor: add clarification about using a reverse proxy endpoint (#135537) * [GeoIP processor] Add clarification about using a reverse proxy endpoint --- docs/reference/ingest/processors/geoip.asciidoc | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/docs/reference/ingest/processors/geoip.asciidoc b/docs/reference/ingest/processors/geoip.asciidoc index 8246d881229e6..bb42bcd175af3 100644 --- a/docs/reference/ingest/processors/geoip.asciidoc +++ b/docs/reference/ingest/processors/geoip.asciidoc @@ -343,18 +343,20 @@ 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. +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: