Chris,
Any update on this? Did you have a chance to have a look on the PR?
Lazar
On Wed, Mar 4, 2020 at 10:55 AM Lazar Kirchev
wrote:
> Chris, Martin,
>
> Here is the PR: https://github.com/apache/tomcat/pull/252
>
> Lazar
>
> On Sat, Feb 29, 2020 at 8:27 AM Martin Grigorov
> wrote:
>
>> On F
On Tue, Mar 10, 2020 at 3:56 PM Christopher Schultz <
ch...@christopherschultz.net> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Martin,
>
> On 3/10/20 04:43, Martin Grigorov wrote:
> > We can define custom address like "loopback" for which Tomcat will
> > bind on both "127.0.0.1
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin,
On 3/10/20 04:43, Martin Grigorov wrote:
> We can define custom address like "loopback" for which Tomcat will
> bind on both "127.0.0.1" and "::1" depending on the values of
> java.net.preferIPv4Stack and java.net.preferIPv6Addresses, but I
Hi,
On Tue, Mar 10, 2020 at 10:00 AM "Jürgen Göres" wrote:
>
>
> Hi Mark,
>
> so I went with your proposed default setting of "::".
> Alas, this fails, e.g., when we put our Tomcats into Docker containers,
> where only IPv4 is available (I would expect the same to happen on AWS
> environments, w
Hi,
On Mon, Mar 9, 2020 at 9:34 PM Piyush Kumar Nayak
wrote:
> There appears to be a change in the behavior of AJP connector in Tomcat,
> with respect to the protocol stack of the loopback address it binds to.
> With older versions it binds to both IPv6 and IPv4 interface, but with
> 9.0.31 it a
Hi Mark,
so I went with your proposed default setting of "::".
Alas, this fails, e.g., when we put our Tomcats into Docker containers, where
only IPv4 is available (I would expect the same to happen on AWS environments,
which are usually IPv4 only, too, haven't checked that yet):
10-Mar-20
Hi Alexandre,
You should sent an email to users-unsubscr...@tomcat.apache.org instead.
See https://tomcat.apache.org/lists.html#tomcat-users
On Mon, Mar 9, 2020 at 8:52 PM Alexandre Adao wrote:
> users@tomcat.apache.org
>
