Why I quit using Bearshare 2.3.0
 

It rejected My Napster and Gnucleus users. They couldn't upload from me. Net result was a CONSTANT barrage of requests that wouldn't transfer.

Needless to say, I went back to 2.2.7

Changing file transfer protocol was idiotic. I hope the developer
had a good reason to do it.

Version 1.4.2 of gnucleus can download from bearshare. It was a major factor in the release.

I see bearshare is returning a 206 code now on partial downloads. Is this what was causing the trouble or was it something else?

Looking at the HTTP/1.1 RFC it at least seems it's the correct reply for a partial response - I guess I can't be too critical of it if that's the case. ;-)

the correct response for a file transfer is
content-length: bytes=1234324

but the new version of bearshare droped the equal sign from the header so it was just
content-length: bytes 1234324

causing the parser in gnucleus to screw up. I'm not sure if any other clients were messed by this change.

Ahh! Thanks for the info - I guess I *can* be critical of BearShare then! ;-)

But.
 

The way Bearshare does it is actually the true HTTP/1.1 Spec.
The reason most Gnutella clients use the "=" is that the nulsoft Gnutella/0.56 used it.

Here is a link:
http://groups.yahoo.com/group/the_gdf/message/2549