You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
i've recently run into an issue using the GeoIP.dat files downloaded from https://www.miyuru.lk/geoiplegacy
while the file is working as expected for nginx, it is being used by a Magento 1 module (Openstream/GeoIP) to provide geoip redirects.
After investigating the module and testing with the last published GeoIP.dat file from MaxMind, it seems that the
database type (set as COUNTRY_EDITION) in the MaxMind DB is value 106, where as in geolite2legacy the constant has a value 1
other than the magento module not accepting the geolite2legacy generated file, everything else appears to be happy with the difference in the database type value (geoiplookup tools, nginx) - but it could be that they are just assuming default values for things if the type value doesn't match something else.
The text was updated successfully, but these errors were encountered:
I was using a old version of sherpya/geolite2legacy from 01/2019. Now I am using the lastest geolite2legacy for the releases from 09/2020. Please try the new releases.
Further more, I recommend contacting me via email or twitter for releases from my site.
Before creating an issue here please double check the error by creating a db from sherpya/geolite2legacy as I do custom modifications for releases on my site.
Hi,
i've recently run into an issue using the GeoIP.dat files downloaded from https://www.miyuru.lk/geoiplegacy
while the file is working as expected for nginx, it is being used by a Magento 1 module (Openstream/GeoIP) to provide geoip redirects.
After investigating the module and testing with the last published GeoIP.dat file from MaxMind, it seems that the
database type (set as COUNTRY_EDITION) in the MaxMind DB is value 106, where as in geolite2legacy the constant has a value 1
other than the magento module not accepting the geolite2legacy generated file, everything else appears to be happy with the difference in the database type value (geoiplookup tools, nginx) - but it could be that they are just assuming default values for things if the type value doesn't match something else.
The text was updated successfully, but these errors were encountered: