MPR Vaadin 7 app Push issue

Flow
1

What does communication.PushHandler:84 - Invalid identifier in new connection received from 0:0:0:0:0:0:0:1 mean and is it something I need to worry about?

2

Is your environment using ip6?

3

It is a Windows 10 machine with pretty standard setup ( I did not touch the network settings, just used defaults ). According to https://ipv6-test.com/ and http://v6.testmyipv6.com/, I can use ip6. According to http://testmyipv6.com, I am using ip4. According to windows setup, I have both a ip6 and ip4 addresses. When I run ipconfig on this machine, I get the following for my wireless ( numbers and letters replaced with “#” out of paranoia ):

Wireless LAN adapter Wi-Fi:

   Connection-specific DNS Suffix  . : attlocal.net
   IPv6 Address. . . . . . . . . . . : ####:####:####:####::####
   IPv6 Address. . . . . . . . . . . : ####:####:####:####:####:####:####:####
   Temporary IPv6 Address. . . . . . : ####:####:####:####:####:####:####:####
   Temporary IPv6 Address. . . . . . : ####:####:####:####:####:####:####:####
   Temporary IPv6 Address. . . . . . : ####:####:####:####:####:###:####:####
   Temporary IPv6 Address. . . . . . : ####:####:####:####:####:###:####:####
   Temporary IPv6 Address. . . . . . : ####:####:####:####:####:####:####:####
   Link-local IPv6 Address . . . . . : ####::####:####:####:####%8
   IPv4 Address. . . . . . . . . . . : ###.###.#.##
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . : ####::####:####:####:####%8
                                       ###.###.#.###

I am not sure if any of that answers your question. It seems my computer chooses the best option for whatever I am doing.

What is weird is that I don’t remember this problem with the pure Vaadin 7 app.

4

OK, when I moved to another network ( coffee shop, so not as good as home ), I don’t get the warning. When I checked ipconfig and the URLs above, I see I do not have ip6 ( ipconfig does not have an ip6 address, etc ). So I will get this warning anytime I go to a network that supports ip6? Is it something I should worry about?

5

It looks like the fix we have included in our legacy framework is not included in the Atmosphere version used in Flow

https://github.com/vaadin/framework/issues/11458

6

I cannot tell from the issue you specified, but is it an issue that will be fixed?

Or, conversely, is it safe to ignore?