You're right, Upstream hasn't issued a response. At least, not on that
thread. I reached out to NGINX directly and got a "We're not adjusting
the GeoIP module" answer.
TO THAT END, however, downstream in Ubuntu we packaged the third party
geoip2 module as its own independent of the core GeoI
On Thu, Jan 31, 2019 at 04:36:45PM -0500, Thomas Ward wrote:
> The GeoIP module is a core module in NGINX upstream. Keeping this in
> mind, it's just packaged here as a dynamic module.
>
> For reference purposes, I have forwarded this bug report to nginx
> upstream's nginx-devel mailing list [1]
Hi.
The GeoIP module is a core module in NGINX upstream. Keeping this in
mind, it's just packaged here as a dynamic module.
For reference purposes, I have forwarded this bug report to nginx
upstream's nginx-devel mailing list [1] for their response.
(Note that this is just me adding information
Package: libnginx-mod-http-geoip
Version: 1.14.2-2
Severity: important
Dear maintainer,
In its current form, the geoip module for nginx depends on the MaxMind GeoIP
database in the Legacy format, the free version of which (GeoLite Legacy) has
been deprecated since January 2018 and discontinued at
4 matches
Mail list logo
