Skip to content

Commit 891166c

Browse files
authored
Update geoip.asciidoc (#107094)
The documention mention that we can use the proxy. But here the workaround mention the usage of reverse proxy The proxy feature for geoip download is not yet supported #77069 (comment)
1 parent f7fd810 commit 891166c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

docs/reference/ingest/processors/geoip.asciidoc

+4-4
Original file line numberDiff line numberDiff line change
@@ -321,15 +321,15 @@ GET /my_ip_locations/_search
321321
If you can't <<geoip-automatic-updates,automatically update>> your GeoIP2
322322
databases from the Elastic endpoint, you have a few other options:
323323

324-
* <<use-proxy-geoip-endpoint,Use a proxy endpoint>>
324+
* <<use-reverse-proxy-geoip-endpoint,Use a reverse proxy endpoint>>
325325
* <<use-custom-geoip-endpoint,Use a custom endpoint>>
326326
* <<manually-update-geoip-databases,Manually update your GeoIP2 databases>>
327327

328-
[[use-proxy-geoip-endpoint]]
329-
**Use a proxy endpoint**
328+
[[use-reverse-proxy-geoip-endpoint]]
329+
**Use a reverse proxy endpoint**
330330

331331
If you can't connect directly to the Elastic GeoIP endpoint, consider setting up
332-
a secure proxy. You can then specify the proxy endpoint URL in the
332+
a secure reverse proxy. You can then specify the reverse proxy endpoint URL in the
333333
<<ingest-geoip-downloader-endpoint,`ingest.geoip.downloader.endpoint`>> setting
334334
of each node’s `elasticsearch.yml` file.
335335

0 commit comments

Comments
 (0)