Tuc at T-B-O-H.NET wrote:
Hi,
There seemed to have been some discussion back in October
about BitTorrent. I just noticed that I had :
2008/06/10 03:02:39| parseHttpRequest: Requestheader contains NULL characters
2008/06/10 03:02:39| parseHttpRequest: Unsupported method '^SBitTorrent'
2008/06/10 03:02:39| clientReadRequest: FD 27 (192.168.3.15:64673) Invalid Request
and
2008/06/10 05:02:01| parseHttpRequest: Unsupported method '<C1><94>V^W<A9>uk<DB>J8a<CB><BF>mx'2^_I<F5><DF><CE><97><F5>Mj<C4><97><B4><94><81>|<CE><9D><90><B3>
<9F>^W^P<BB>^Q<9D><EB>G<E2>/<87>S<C3>J<92><B6><94><AB><F8>J<BD><FA>?\8^_,<FC>y
<F7>^P<B0><F6><9D>1<96><EF><D9><BE><A0>E<90>xp<C1><C7>^?XRf^<86>^R<AD><AD><D6>i
^A^E(<AC><D9>^B<C4>-x<AC><C2>^Da<E4>ESC<8D>T<DB>^X<FE>^Z9
'
2008/06/10 05:02:01| clientReadRequest: FD 28 (192.168.3.15:58694) Invalid Request
dotted through my logs.
I was just wondering if anything ever came of the discussion. It looks
like the user was trying to do it proxied, then stopped for 20 minutes, and
then found some other way out.
I don't care if they use it, just wondered if there was a way to
fully support it.
It's on my todo list a fair way down. Probably around 3.3.
From 3.1 we have dropped a lot of the 'unsupported methods' issues. So
the first attempts may get through.
I'd put it down to a broken client software through. All the torrents I
use are proxied properly and working.
Amos
--
Please use Squid 2.7.STABLE1 or 3.0.STABLE6
