Windows - fix connecting to a socket using IPv4 mapped IPv6
authorShane Kearns <ext-shane.2.kearns@nokia.com>
Fri, 17 Feb 2012 20:33:57 +0000 (20:33 +0000)
committerQt by Nokia <qt-info@nokia.com>
Mon, 20 Feb 2012 17:20:20 +0000 (18:20 +0100)
commit4bb020f50b5cc8656a17b217c04e662d88cb795c
tree6aa6a4ab04abec1240e82b871fd68e9b8ac05854
parent054114a459580b71e170dc6bf356e8943d0ed068
Windows - fix connecting to a socket using IPv4 mapped IPv6

Connecting to an IPv4 mapped IPv6 address (e.g. ::FFFF:127.0.0.1)
requires the IPV6_V6ONLY socket option to be cleared.
This was causing tst_qtcpserver::ipv6ServerMapped autotest to fail.
The same change is not required on MacOS X - the test passes there.

Task-number: QTBUG-24351
Change-Id: I6c08b19f0daa12765da2d44792ffb17299322695
Reviewed-by: Markus Goetz <markus@woboq.com>
Reviewed-by: Thiago Macieira <thiago.macieira@intel.com>
src/network/socket/qnativesocketengine_win.cpp