![]() |
|
Register | FAQ | The Twelve Commandments | Members List | Calendar | Arcade | Find the Best VPN | Today's Posts | Search |
| LinkBack ![]() | Thread Tools ![]() | Display Modes ![]() |
|
| |||
![]() Oh, is that what LimeWire clients do? Clip their requests to the ranges available? Regardless, clients that don't clip their requests should not be given a 416 in this situation. I think it is more likely that the LW developers intend to follow RFC2616, the HTTP 1.1 spec: 10.4.17 416 Requested Range Not Satisfiable A server SHOULD return a response with this status code if a request included a Range request-header field (section 14.35), and none of the range-specifier values in this field overlap the current extent of the selected resource, and the request did not include an If-Range request-header field. (For byte-ranges, this means that the first- byte-pos of all of the byte-range-spec values were greater than the current length of the selected resource.) |
| |
![]() | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
PLEASE someone try to help me, I am not getting any response to this. | bart robinson007 | General Mac OSX Support | 1 | February 14th, 2007 04:32 AM |
IP Ranges Help Filter Hosts Not Working | cheg | General Windows Support | 0 | February 7th, 2007 09:23 AM |
banned IP ranges | MoJoJoJo | New Feature Requests | 7 | May 8th, 2004 02:15 AM |
Feature request: boycotting IP ranges | amatulic | New Feature Requests | 15 | June 6th, 2002 10:51 AM |
How to filter by IP ranges? | Unregistered | Download/Upload Problems | 0 | April 28th, 2002 04:01 PM |