Description
Type of issue
Missing information
What documentation page is affected
https://www.elastic.co/docs/reference/enrich-processor/geoip-processor
What happened?
The documentation page https://www.elastic.co/docs/reference/enrich-processor/geoip-processor#use-proxy-geoip-endpoint mentions Use a proxy endpoint, which could be misconstrued as standard HTTP proxy support.
However, the ingest.geoip.downloader.endpoint setting is only applicable when using a custom endpoint or a reverse proxy. As noted in issue #77069, true HTTP proxy support for GeoIP database downloads is not currently available in Elasticsearch.
In essence, the documentation could be clearer in distinguishing between using a reverse proxy (which is supported) and a general HTTP proxy (which is not).
While the documentation for Elasticsearch 8.13 https://www.elastic.co/guide/en/elasticsearch/reference/8.13/geoip-processor.html#use-reverse-proxy-geoip-endpoint was corrected as part of this issue: #86964, this fix doesn't appear to have been consistently applied to later versions of the documentation.
cc @frconil
Additional info
No response