send proper 416 responses

416 responses without a body should respond with a zero
Content-Length and a Content-Range that allows clients
to specify a proper range in the future.

rfc2616, section 14.16 says:
> A server sending a response with status code 416 (Requested
> range not satisfiable) SHOULD include a Content-Range field
> with a byte-range- resp-spec of "*". The instance-length
> specifies the current length of the selected resource.

0 files changed, 0 insertions, 0 deletions