Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:cache:common:geoip-support [2019/04/17 14:52]
Lisa Clarke [Advanced Configuration:GEOIP2 Envirment Variables] Copyediting
+++ litespeed_wiki:cache:common:geoip-support [2020/01/16 16:22]
Jackson Zhang
@@ Line 1: / Line 1: @@
 ====== GeoLocation support (GEOIP) for LiteSpeed Web Server  ======
-LSCache supports GEOIP.
+LSCache supports GEOIP, including MaxMind GeoIP2 database, MaxMind GeoIP Legacy Database and IP2Location DB.  MaxMind discontinued Legacy databases On January 2, 2019 hence we recommend not to use it anymore.
 For LSWS v5.2.x and earlier, only the MaxMind Legacy Database .dat is supported. As of LSWS v5.3RC2, LSWS supports the [[https://www.maxmind.com/en/geoip2-databases|MaxMind GeoIP2 format database]], ''.mmdb''. The database path configuration is in the same location as the legacy DB (**Configuration > Server > General > General settings > IP to GeoLocation DB**), then set the database path to either ''.dat'' or ''.mmdb''.
@@ Line 89: / Line 89: @@
 You can add the following:
   GEOIP_REGION_NAME CITY_DB/subdivisions/0/names/en
-Please make sure the correct entry name is used. For example, the following is incorrect.
+Please make sure the correct entry name is used. For example, the following is incorrect: ''name'' should be ''names''.
   GEOIP_REGION_NAME CITY_DB/subdivisions/0/name/en
@@ Line 149: / Line 149: @@
 It may return the database path as <code>/usr/share/GeoIP/GeoIP.dat</code>
-Alternatively, you can just download the database yourself directly.
 **NOTE**: On January 2, 2019, MaxMind discontinued the GeoLite Legacy databases. GeoLite Legacy databases are no longer available for download.
@@ Line 262: / Line 260: @@
 GeoIP rewrite rules that do not work as expected may be more complicated. You will need to check the rules to look for issues such as a redirect loop. When needed, you can log a ticket with us. Let us know the rules set is not working as expected, and provide a more detailed test example for us to take a further look.
-==== Out of date database caused IP not blocked ====
+==== IP Not Blocked Due to Out-of-date Database ====
-A user setup the following at /etc/apache2/conf.d/userdata/geoip.conf:
+A user set up the following at ''/etc/apache2/conf.d/userdata/geoip.conf'':
   <IfModule mod_geoip.c>
@@ Line 271: / Line 269: @@
   </IfModule>
-Tested from an IP x.x.x.x (NG/Nigeria/-), it should be blocked but it didnot.
+Testing from an IP in NG/Nigeria/- ''x.x.x.x'', it should be blocked but it is not.
-Further analysis showing the above IP blongs to North Carolina, US in that downloaded MaxMind database and look like the record on that old database is incorrrect. If the database is not kept up to date, it will result in incorrect information.
+Further analysis shows the above IP belongs to North Carolina, US in the downloaded MaxMind database. It looks like the record on that old database is incorrrect. If the database is not kept up to date, it will result in incorrect information.
-You can keep the database up to date from time to time manually by doing a direct download of the database, or you can use the [[https://dev.maxmind.com/geoip/geoipupdate/|geoipupdate -tool]], so your system automatically keeps the file up to date whenever MaxMind updates the records in the database.
+You can keep the database up to date from time to time manually by doing a direct download, or you can use the [[https://dev.maxmind.com/geoip/geoipupdate/|geoipupdate tool]], so your system automatically keeps the file up to date whenever MaxMind publishes an update.