docs: clarify custom GeoJSON URL requirements for area maps#650
Open
mintlify[bot] wants to merge 1 commit into
Open
docs: clarify custom GeoJSON URL requirements for area maps#650mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
🤖 Documentation Bot✅ All checks passed! No issues found. |
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
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
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.
Summary
Documents the requirements that custom GeoJSON URLs must satisfy when used in area (choropleth) maps, so users can troubleshoot URLs that fail to load.
Changes
Context
The upstream change tightened the server-side proxy that fetches custom GeoJSON files: it now validates the resolved IP against a broader set of private/reserved ranges, pins the connection to a pre-validated address to prevent DNS rebinding, and rejects redirects outright. These are user-visible constraints — previously valid URLs that redirect or resolve to private/CGNAT space will now fail — so they are worth surfacing in the map documentation.