Follow-up Comment #5, bug #47906 (project gnash):
I have tested several programs regarding the behavior on connecting to
dual-stack TCP server on localhost. (Dual-stack in this case means host name
lookup returns both IPv4 and IPv6 address)
* GNU Wget (`wget http://localhost:2229/`): connects IPv6 first. If fails,
tries IPv4.
* Debian Iceweasel (`iceweasel http://localhost:2229/`): connects IPv6 first.
If fails, tries IPv4.
* Curl HTTP (`curl http://localhost:2229/`): connects IPv6 first. If fails,
tries IPv4.
* Hobbit's Netcat (`nc localhost 2229`): connects IPv4 only.
If the server listened with IPv4 (ordinary AF_INET) socket, an attempt to
connect to server's IPv6 address will fail (_"Connection refused"_) while IPv4
succeeds. But if the server listened with IPv6 (AF_INET6) socket, an attempt
to connect to server's IPv4 *or* IPv6 address would succeed.
For current Gnash's behavior:
* Gnash HTTP (via libcurl): connects IPv6 first. If fails, tries IPv4.
* Gnash FTP (via libcurl): connects IPv6 first. If fails, tries IPv4.
* Gnash RTMP (via libcurl): connects IPv6 first. If fails, tries IPv4.
* *Gnash XMLSocket: connects IPv6 only.*
Wget: 1.13.4 (debian)
Iceweasel: 10.0.12 (debian)
Curl: 7.26.0 (debian)
Netcat: 1.10-40 (debian)
Gnash: 0.8.11dev (git c6da486 10-May-2016)
System: Debian GNU/Linux 7.0 Wheezy i386
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?47906>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/