[8.19][DOCS] GeoIP processor: add clarification about using a reverse proxy endpoint #135537
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
vishaangelova
added
>docs
|
Documentation preview: |
|
@vishaangelova please enable the option "Allow edits and access to secrets by maintainers" on your PR. For more information, see the documentation. |
|
Pinging @elastic/core-docs (Team:Docs) |
elasticsearchmachine
added
external-contributor
nitishaggarwal49
approved these changes
Sep 29, 2025
leemthompo
approved these changes
Sep 29, 2025
vishaangelova
added a commit
to vishaangelova/elasticsearch
that referenced
this pull request
Sep 29, 2025
… proxy endpoint (elastic#135537) * [GeoIP processor] Add clarification about using a reverse proxy endpoint
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR updates the GeoIP processor doc to clarify that users need to use a reverse proxy endpoint to update their IP geolocation databases.
Resolves elastic/docs-content#1240
Related to #135534