<div dir="ltr">Awesome. Seems like https passes TLS handshake and then the same thing.</div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Oct 10, 2014 at 10:40 PM, Phil Mayers <span dir="ltr"><<a href="mailto:p.mayers@imperial.ac.uk" target="_blank">p.mayers@imperial.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">FFS<br>
<br>
$ nc -6 -v <a href="http://www.bt.com" target="_blank">www.bt.com</a> 80<br>
Ncat: Version 6.40 ( <a href="http://nmap.org/ncat" target="_blank">http://nmap.org/ncat</a> )<br>
Ncat: Connected to 2a00:2381:ffff::1:80.<br>
GET / HTTP/1.0<br>
Host: <a href="http://www.bt.com" target="_blank">www.bt.com</a><br>
<br>
Ncat: Connection reset by peer.<br>
<br>
<br>
Maybe I should be glad BT haven't deployed any IPv6 to their residential customers; they'd only find some way to mess up a pretty straightforward task. Like keeping a link up for more than 24 hours.<br>
</blockquote></div><br></div>