<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
<br>> Date: Tue, 2 Feb 2010 02:54:56 -0600<br>> From: bennett@cs.niu.edu<br>> To: downgeoff2@hotmail.com; or-talk@freehaven.net<br>> Subject: RE: client bug in 0.2.2.7-alpha and a new bad exit: exoassist<br>> <br>> <snip><br>> The real<br>> destination's name is then passed through the circuit for the exit node<br>> to resolve, but the .nickname.exit has to be stripped by tor at some point<br>> for that to work.<br>> So it looks to me as though 0.2.2.7-alpha has introduced a client bug.<br><br>I don't know the technicalities of SOCKS proxies, but I'm 95% certain that .exit notation caused errors from destination servers over a year ago - it's not a new problem.<br>Of course some servers aren't running virtual hosts and so don't care about the<br>"Host: example.com.nickname.exit"<br>header - perhaps you just haven't come across the problem before if you don't use .exit notation much?<br>Perhaps one of the developers could weigh in on whether Tor itself should be modifying the Host header - it may be moot as .exit notation is deprecated now (and the whole excludenodes business under review).<br><br>GD<br> <br /><hr />Hotmail: Trusted email with powerful SPAM protection. <a href='http://clk.atdmt.com/GBL/go/201469227/direct/01/' target='_new'>Sign up now.</a></body>
</html>