fixed HTTP chunk bug (must be treated separately from HTTP byte range scenario, yet allow sequential access to ByteStream "ranges", i.e. consecutive chunks)