Thank you for providing guidance on this topic, I really appreciate it!
Have a great day!
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,292821,292830#msg-292830
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listin
Hello!
On Mon, Nov 15, 2021 at 08:46:29AM -0500, YvorL wrote:
> Hi Maxim,
>
> I really appreciate your response!
> I just realized that in the background I'm converting the current GeoIP2
> database to legacy format (https://github.com/sherpya/geolite2legacy).
>
> As I mentioned before, when I
Hi Maxim,
I really appreciate your response!
I just realized that in the background I'm converting the current GeoIP2
database to legacy format (https://github.com/sherpya/geolite2legacy).
As I mentioned before, when I logged $geoip_region, I got a full string
instead of 2 symbols as it's define
Hello!
On Sun, Nov 14, 2021 at 12:54:47PM -0500, YvorL wrote:
> I see. It's weird that I can't use a column that's right there in the
> database and would uniquely identify any entry.
That's because there is no such column in the database nginx uses.
Note that GeoIP modules uses GeoIP database
Thank you for your response!
I see. It's weird that I can't use a column that's right there in the
database and would uniquely identify any entry.
When I checked the Nginx documentation, I saw this:
"$geoip_region
two-symbol country region code (region, territory, state, province, federal
land an
Hello!
On Fri, Nov 12, 2021 at 09:21:58AM -0500, YvorL wrote:
> I was setting up GeoIP rules
> (https://nginx.org/en/docs/http/ngx_http_geoip_module.html) and looked into
> the MaxMind database when I realized there are multiple cities that has the
> same name. This means I can't simply match $ge
I was setting up GeoIP rules
(https://nginx.org/en/docs/http/ngx_http_geoip_module.html) and looked into
the MaxMind database when I realized there are multiple cities that has the
same name. This means I can't simply match $geoip_city in a rule. The only
data that's unique and is available for all
