Content-Length must be ignored if any Transfer-Encoding is present in the response. Refer to RFC 7230 section 3.3.3 and RFC2616 section 4.4. This is figured out here after all headers have been received but before the final call to the user's header callback, so that a valid content length can be retrieved by the user in the final call. */
source not stored for this graph (policy: none)
no test coverage detected