Geo targeting

Strict matching

Control what happens when the exact geo target has no available IP. These are username flags on proxy.geonode.io.

Auth

Use your Geonode proxy username and password with the proxy URL.

Username syntax

FlagBehavior
(omit) / -strict-onStrict match. If the exact location is unavailable, the request fails.
-strict-offAllow fallback to another location in the same country when possible.
<geonode_username>-country-<COUNTRY>-city-<city>-strict-on:<geonode_password>
<geonode_username>-country-<COUNTRY>-city-<city>-strict-off:<geonode_password>

Works with country / state / city / asn targeting. Prefer always including -country-.

Parameters

NameInRequiredDescription
strict-on / strict-offusername flagnoDefault behavior is strict (same as -strict-on)
geo flagsusername flagyesAt least one geo target (usually -country- plus city/state/asn)

Examples

Fallback allowed (-strict-off)

fake city with -strict-off still returned a US IP.

curl -x "http://proxy.geonode.io:<port>" \
  --proxy-user "<geonode_username>-country-US-city-zzznomatchcity-strict-off:<geonode_password>" \
  "http://ip-api.com/json"

Example egress (US fallback):

{
  "status": "success",
  "country": "United States",
  "countryCode": "US",
  "region": "PA",
  "regionName": "Pennsylvania",
  "city": "Mountain Top",
  "zip": "18707",
  "lat": 41.1695,
  "lon": -75.8777,
  "timezone": "America/New_York",
  "isp": "PenTeleData Inc.",
  "org": "PenTeleData House Account",
  "as": "AS3737 PenTeleData Inc.",
  "query": "50.29.236.79"
}

Strict (-strict-on) when location missing

same fake city with -strict-on failed with HTTP 465 (Can Not Fulfill Targeting).

curl -x "http://proxy.geonode.io:<port>" \
  --proxy-user "<geonode_username>-country-US-city-zzznomatchcity-strict-on:<geonode_password>" \
  "http://ip-api.com/json"

Expect an error response from the proxy (not a normal ip-api JSON body). See Error Handling for 465.

Was this page helpful?

On this page