Abivia Geocoding 2.6.0 and 2.5.1
January 6, 2025
Geocoding 2.5.1 fixed an issue where an invalid value is passed through the HTTP_X_FORWARDED_FOR
header, automatically returning the REMOTE_ADDR
instead.
However, some bad actors will supply a Bogon or a valid but incorrect address (e.g. 127.0.0.1).
Geocoding 2.6.0 adds a $allowForward parameter to the GeoCoder::getAddressFromHttp()
and GeoCoder::lookupHttp()
methods. The parameter defaults to true.
This allows an application to get the REMOTE_ADDR
from the server when a bad forwarder is present.