i just located all the HTTP header info in XoloX


GNUTELLA CONNECT/0.4
get /get/
HTTP/1.0
User-Agent: www.XoloX.nl
Referer: Gnutella

it would not be hard for me to change that to something totally different.

i could also check BearShare's connection info and possibly mimic it for each release they do. (no promisses though- it might not be possible)

i could change that stuff, and release a 1.16 client of both my Xenomorph dot Net version, and Zeropaid (if they want me to)...

BS Blocks *all* v0.4 connections, so that would mean you'd have to connect with Xolox to a Gnutella deamon or something similar. Just FYI, I'll continue to support 0.4.

Yes,

I think all clients will support 0.4, perhaps Limewire not...

Morgwen

0.4 connection uses 0A 0A (\n\n)

06. connection uses 0D 0A (\r\n)

there was only 0A 0A in XoloX.

ive tried different changes in the connection string, and i cant get XoloX to connect any after making the changes.

here are the connection strings used by Gnutella clients:

Connecting Version 0.4 :


GNUTELLA CONNECT/0.4\n\n

GNUTELLA OK\n\n



Connecting Version 0.6:

GNUTELLA CONNECT/0.6\r\n
User-Agent: Program Name v1.0\r\n
\r\n


GNUTELLA/0.6 200 OK\r\n
User-Agent: Program Name v1.0\r\n
\r\n


GNUTELLA/0.6 200 OK\r\n
\r\n

or better yet, how do we block 0.6 connections?

Bearshare is blocking "ALL" other clients... their hostcaches only accept "OWN" bearshare nodes!

More input!

http://www.gnutellaforums.com/showth...8237#post28237

Morgwen

We're no longer supporting XoloX.

dear vinnie,
f' you
enough said

if xolox sux so bad why is it alive and kicking?
why is it's undevelpoing *** doin alright raw?
why not imitate xolox instead of eliminating xolox?
unless this internet thingy becomes a proprietary network maybe we should keep it open?
bearshare has deemed xolox the ******.
write better code not exculsionary code.
innovate otherwise open your mouth n masterbate

use this and block back
http://opensourcep2p.sf.net