On 05/03/2020 07:12, "Jürgen Göres" wrote: >>> My first question is: what value do I need to set in the "address" >>> attribute to indicate that I want the connector to listen on ALL interfaces >>> (for IPv4 AND IPv6)? Maybe that should be documented. :-) >> >> It will vary by system. Some systems can't listen on both IPv4 and IPv6 >> with a single socker. Usually either "::" or "0.0.0.0" will have the >> desired result. > > That is a bit of a problem for us. In the environments we support (Win and > Linux), from my observation the connectors would successfully bind to both > IPv4 and IPv6 addresses. Since we have customers that use either IPv4, IPv6, > or both and often have multiple interfaces on their machines, we cannot know > which address/interface (or even which IP version) to bind to. And up to now, > we didn't have to worry about it. > Now our installation routine would somehow need to find out whether it should > put a "::" or a "0.0.0.0" in the "address" attribute. What was "zero conf" > for us so far now suddently becomes a new source for problems (=customer > calls). > Is there no way to optionally configure the old binding behaviour for the AJP > connector?
Let me re-phrase. Usually, for the NIO and NIO2 Connectors, specifying "::" or "0.0.0.0" will result in the server socket binding to all IPv4 and IPv6 addresses. For APR/Native, "0.0.0.0" will be IPv4 only. "::" will be IPv4 and IPv6. If the underlying OS does not support "dual stack" networking (most do), "0.0.0.0" will result in listing on all IPv4 addresses and "::" will result in listening on all IPv6 addresses. For your use case "::" looks like the best default. Most of this is in the docs for the HTTP Connector. I'll add the same text to the AJP Connector. Mark --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
