Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
litespeed_wiki:cache:common:geoip-support [2019/04/16 17:58] Jackson Zhang |
litespeed_wiki:cache:common:geoip-support [2019/04/16 20:25] Jackson Zhang |
||
|---|---|---|---|
| Line 46: | Line 46: | ||
| </code> | </code> | ||
| - | ==== GEOIP2 Envirment Variables ==== | + | ==== Advanced Configuration:GEOIP2 Envirment Variables ==== |
| The full power of the GeoIP2 facility requires use of the environment variables in the Litespeed Configuration. The description of the format used is designed to be as similar as possible as the Apache mod_maxminddb environment described [[https://github.com/maxmind/mod_maxminddb|here]] specifically for the MaxMindDBEnv variable. Each environment variable is specified in the environment text box as one line: | The full power of the GeoIP2 facility requires use of the environment variables in the Litespeed Configuration. The description of the format used is designed to be as similar as possible as the Apache mod_maxminddb environment described [[https://github.com/maxmind/mod_maxminddb|here]] specifically for the MaxMindDBEnv variable. Each environment variable is specified in the environment text box as one line: | ||
| Line 261: | Line 261: | ||
| | | ||
| 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. | 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 ==== | ||
| + | A user setup the following at /etc/apache2/conf.d/userdata/geoip.conf: | ||
| + | |||
| + | <IfModule mod_geoip.c> | ||
| + | RewriteEngine on | ||
| + | RewriteCond %{ENV:GEOIP_COUNTRY_CODE} !^(GB|DK|US|IN)$ | ||
| + | RewriteRule (wp-login|xmlrpc)\.php$ - [F,L] | ||
| + | </IfModule> | ||
| + | |||
| + | Tested from an IP x.x.x.x (NG/Nigeria/-), it should be blocked but it didnot. | ||
| + | |||
| + | 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. | ||
| + | |||
| + | 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. | ||