Matthew Toseland wrote:
You can't have a 206 in response to a request that didn't ask for a
byterange:
Damn. I suppose you could try to trick the client into sending a range
request by sending a 416 (requested range not satisfiable) in response
to the original request, specifying the range that the client should
request... but that's getting really ugly.
Michael
_______________________________________________
Devl mailing list
[email protected]
http://dodo.freenetproject.org/cgi-bin/mailman/listinfo/devl
