© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Opting for #1 is a stupid idea.
Yes, personally I hate it because many times I have been wondering why it's not listening on IPv6 only to find out that the configuration line "listen 80 default_server;" doesn't in fact mean to just listen on port 80, but to listen only on port 80 for IPv4. In my opinion this configuration line doesn't make it clear, and if it stays like this, then "#listen [::]:80 default_server;" needs to be included in this way at the very least (note the hash symbol)!
What is another problem is hosting providers that are dual-stacked, and where maybe AAAA-records already exist. In those cases the client would first try to connect to the IPv6 address which has no nginx listening on port 80. Happy eyeballs should take care of this and fallback to IPv4, but that doesn't always seem to work properly.
On another note this is another step towards cannibalizing the deployment of IPv6 by making it opt-in instead of opt-out. Either implement option #2 or return to the way it was before and leave it up to the admin to figure out why his config doesn't work on the system he fiddled with.