This fixes the phenomenon where during twitch stream prerolls,
a lot of TCP connections are opened / closed rapidly,
instead of the same one(s) being reused for sequential segments
like during normal operation.
The response data always needs to be read from the socket,
otherwise the socket cannot be reused by other HTTP requests
(hence the rapid closing/opening of connections during skipped segments)

Billy2011 added a commit to Billy2011/streamlink-27 that referenced this pull request

based on streamlink#4229
This fixes the phenomenon where during twitch stream prerolls,
a lot of TCP connections are opened / closed rapidly,
instead of the same one(s) being reused for sequential segments
like during normal operation.
The response data always needs to be read from the socket,
otherwise the socket cannot be reused by other HTTP requests
(hence the rapid closing/opening of connections during skipped segments)

Merged