surprising behavior of renderByteRange #86
Description
I had expected (hRange, renderByteRange (ByteRangeFrom 1000)) would be a http request Range header, but in fact renderByteRange does not include the "bytes=" part, so that generates an invalid "Range: 1000-" header.
renderByteRanges does include the "bytes=" part, so the workaround is to use
(hRange, renderByteRanges [ByteRangeFrom 1000])
The only way to learn of either behavior is to read the source code. This at least needs to be documented better.
It might be useful to parameterize the rendering functions with the role the range is being rendered for, eg a Request or a Response. See also #64.