Struct BodyReaderCopy item path

A reader of the response data.

1. If Transfer-Encoding: chunked, the returned reader will unchunk it and any Content-Length header is ignored.
2. If Content-Encoding: gzip (or br) and the corresponding feature flag is enabled (gzip and brotli), decompresses the body data.
3. Given a header like Content-Type: text/plain; charset=ISO-8859-1 and the charset feature enabled, will translate the body to utf-8. This mechanic need two components a mime-type starting text/ and a non-utf8 charset indication.
4. If Content-Length is set, the returned reader is limited to this byte length regardless of how many bytes the server sends.
5. If no length header, the reader is until server stream end.
6. The limit in the body method used to obtain the reader.

Note: The reader is also limited by the Body::as_reader and Body::into_reader calls. If that limit is set very high, a malicious server might return enough bytes to exhaust available memory. If you’re making requests to untrusted servers, you should use set that limit accordingly.

§Example

use std::io::Read;
let mut res = ureq::get("http://httpbin.org/bytes/100")
    .call()?;

assert!(res.headers().contains_key("Content-Length"));
let len: usize = res.headers().get("Content-Length")
    .unwrap().to_str().unwrap().parse().unwrap();

let mut bytes: Vec<u8> = Vec::with_capacity(len);
res.body_mut().as_reader()
    .read_to_end(&mut bytes)?;

assert_eq!(bytes.len(), len);