Thread: 416 response, even though ranges overlap
View Single Post
  #3 (permalink)  
Old September 15th, 2004
mickish mickish is offline
Disciple
  
Join Date: January 22nd, 2004
Location: Miami Beach
Posts: 16
mickish is flying high
Default
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.)