Changes between Initial Version and Version 1 of Ticket #2482, comment 5
- Timestamp:
- 04/17/23 10:48:33 (20 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #2482, comment 5
initial v1 4 4 The thing is: It should not be simplified to configure dualstack. There can be a discussion if nginx should default on IPv6, dualstack or the old behavior (which was dualstack). But changing the default form dualstack to the deprecated IPv4 even if the user configured it the other way on system side is absolutely shitty. 5 5 > and results depend on the system configuration and Apache2 compilation options 6 Yes. And adhering configurations should be the default. All the time. You can add options overwriting system configurations. But having a software that resolves * to 0.0.0.0 while the system resolve * to :: is equivalent shitty as a software resolving nginx.org to 34.199.147.133 .6 Yes. And adhering configurations should be the default. All the time. You can add options overwriting system configurations. But having a software that resolves * to 0.0.0.0 while the system resolve * to :: is equivalent shitty as a software resolving nginx.org to 34.199.147.133 because the developer thinks apache on AWS would be a better solution than nginx. 7 7 > and rejects listens on specific IP addresses if a wildcard listen exists 8 8 And I think this is a good thing. Usually this is a configuration error. You can use reuseaddr if you are sure that you do not like this behavior.