[DOC] Wording in GeoIP instructions for database download can lead to confusion

[lucabelluccini]

Elasticsearch Version

7.14+

Installed Plugins

No response

Java Version

bundled

OS Version

N/A

Problem Description

The documentation page https://www.elastic.co/guide/en/elasticsearch/reference/current/geoip-processor.html#manage-geoip-database-updates contains Use a proxy endpoint, but this can be intended/misread as a real HTTP Proxy.

Instead, the setting ingest.geoip.downloader.endpoint can only be used in concomitance with the solution Use a custom endpoint or putting in place a reverse proxy.

According to the issue #77069, HTTP Proxy support is not yet available.

I think we would need to have settings similar to the ones in Watcher (https://www.elastic.co/guide/en/elasticsearch/reference/current/notification-settings.html#general-notification-settings) (e.g. xpack.http.proxy.*).

Steps to Reproduce

N/A

Logs (if relevant)

No response

[elasticmachine]

Pinging @elastic/es-docs (Team:Docs)

[elasticmachine]

Pinging @elastic/es-data-management (Team:Data Management)

[smalenfant]

I updated the other issue. Reverse proxy endpoint can't work when using 2 metadata with a different endpoint. Also the logging for error updating geoip database [GeoLite2-ASN.mmdb] java.net.SocketTimeoutException: Connect timed out doesn't say anything about URL. Where is it trying to download it from?

[jeanfabrice]

As of April 2023, 8.x documentation is still misleading about the use of Use a proxy endpoint

[fbaligand]

By the way, it would be great to have a real "proxy" setting, so that Elasticsearch can download database updates using a http proxy.