[Pkg-nginx-maintainers] Bug#942817: after re-considerations

Eric Desrochers eric.desrochers at canonical.com
Tue Oct 22 15:43:40 BST 2019


Ok after reconsideration

Here's my new chain of thought

* Scenario #1:

Simply comment out the IPV6 line by default as follow:

server {
listen 80 default_server;
#listen [::]:80 default_server;

I don't expect much impact in the behaviour change. It will only affect
users expecting to have listen ipv6 turn on by default on new installation
or force users to modify their recipes to uncomment the ipv6 listen.

Anyway this config must be used as a starting point/example. Most users
will anyway modify it and overwrite it via puppet/chef/ansible/.....

Note that Centos "nginx-1.16.0-1.el8.ngx.src.rpm" delivers nginx without
ipv6 listen:

# nginx.vh.default.conf
server {
    listen       80;
    server_name  localhost;

So as upstream nginx:
https://github.com/nginx/nginx/blob/master/conf/nginx.conf#L36

So why doing it differently ?

* Scenario #2
I have a preference for Scenario #1 but in case of rejection I would go
with that more hacky-ish approach that I have produced (see my patch)

Thoughts ?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/pkg-nginx-maintainers/attachments/20191022/6094a155/attachment.html>


More information about the Pkg-nginx-maintainers mailing list