BearShare beta testers report seeing LimeWire/4.0.6 respond with 416 Requested Range Unavailable, even though the LW server has part of the requested range:

It would be best if the server would serve as much of the requested range as it can.

http://www.bearshare.net/showthread.php?t=31319

Download to [Host2 IP] ("LimeWire/4.0.6") was Transferring, but now sent statusCode==416
--REQUEST--
GET /uri-res/N2R?urn:sha1:[123] HTTP/1.1\r\n
Host: [Host2 IP]\r\n
User-Agent: BearShare Pro 4.6.0.55\r\n
Range: bytes=76021760-76283903\r\n
Content-Disposition: inline; filename=[ABC].mp3\r\n
X-Gnutella-Content-URN: urn:sha1:[123]\r\n
X-Connection-Type: Other\r\n
X-Features: browse/1.0, queue/0.1\r\n
X-Node: [my IP]\r\n
X-Queue: 0.1\r\n
\r\n

--RESPONSE--
HTTP/1.1 416 Requested Range Unavailable\r\n
Server: LimeWire/4.0.6\r\n
Content-Type: text/plain\r\n
Content-Length: 0\r\n
X-Gnutella-Content-URN: urn:sha1:[123]\r\n
X-Available-Ranges: bytes 0-76099176\r\n
\r\n