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 the beginning of 2019.

https://support.maxmind.com/geolite-legacy-discontinuation-notice/

Paying customers of MaxMind still get access to the GeoIP Legacy database as far
as I can tell, however people who used the royalty-free option such as the
DebConf Video Team can't do that any longer.

To make sure IP Geolocation functionality stays functional long-term in nginx,
please consider providing a GeoIP2 module such as
https://github.com/leev/ngx_http_geoip2_module.

Thanks for your work on nginx!

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, not adding anything 'new'
to this discussion, as it is ultimately up to the maintainers to include
a third party module or not here in Debian)


Thomas

[1]: http://mailman.nginx.org/pipermail/nginx-devel/2019-January/011852.html

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, not adding anything 'new'
to this discussion, as it is ultimately up to the maintainers to include
a third party module or not here in Debian)


Thomas

[1]: http://mailman.nginx.org/pipermail/nginx-devel/2019-January/011852.html

Thanks Thomas! Looking at that thread, upstream doesn't seem to have
issued a response.

That said, Debian is already shipping third-party modules in src:nginx,
under debian/modules. Would it perhaps be acceptable to the nginx
maintainers to include github:leev/ngx_http_geoip2_module in the source
package and include it as a separate binary package?

Whether we should continue to ship the geoip (legacy) module is
orthogonal in a way -- both can be shipped at the same time, although
I'd argue that this is no longer very useful.

Regards,
Faidon

Hello. How are you doing and things in your country these days? Hope you're doing very well and it's peaceful over there.
It's my belief that these revelations were given for us to know the truth and choose the right path accordingly.It would be much appreciated if you acknowledge that the truth must be known to all and make as much effort as possible to promote public awareness of these testimonies.                                                                      Fear is the beginning of wisdom.Just ponder eternity and no way out.
 UK mirror newshttps://www.youtube.com/watch?v=_sRgc9NtHQI  ( unwelcome truth )
https://www.youtube.com/watch?v=dWXkBBIaiVc    a trip to hell  ( extremely graphic )http://heavencometrue.com/?lang=eng    ( web site of the Heaven&Hell eyewitness )

                                                                      unsubscribe

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 GeoIP module.

This was later absorbed at some point into the Debian packages and
applied there, so there IS a libnginx-mod-http-geoip2 available in later
versions of the packaging, at least in Unstable.


Thomas


On Thu, 29 Aug 2019 15:41:56 +0300 Faidon Liambotis wrote:

 > 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] for their response.
 > >
 > > (Note that this is just me adding information, not adding anything
'new'
 > > to this discussion, as it is ultimately up to the maintainers to
include
 > > a third party module or not here in Debian)
 >
 > Thanks Thomas! Looking at that thread, upstream doesn't seem to have
 > issued a response.
 >
 > That said, Debian is already shipping third-party modules in src:nginx,
 > under debian/modules. Would it perhaps be acceptable to the nginx
 > maintainers to include github:leev/ngx_http_geoip2_module in the source
 > package and include it as a separate binary package?
 >
 > Whether we should continue to ship the geoip (legacy) module is
 > orthogonal in a way -- both can be shipped at the same time, although
 > I'd argue that this is no longer very useful.
 >
 > Regards,
 > Faidon
 >
 >

Bbbbg