When the response body has already been limited to the requested range, the emitter should ignore the Content-Range header and emit the full response body.
This looks pretty good. It does not modify existing behavior I guess (at least not a behavior which is covered by tests).
I guess we can supersede #23 for this?
Signed-off-by: Antonio J. García Lagar ajgarcia@c17.net
Description
When the response body has already been limited to the requested range, the emitter should ignore the Content-Range header and emit the full response body.
This is an alternative to #23 to fix #22