WebResponse | Bug in binary-vs-ascii

So, WebClient will pass the 'stream' as-is when creating the WebResponse via #readFrom:. The response will then read the headers.

But there is no code that checks 'content-type' nor 'content-encoding' to set that stream back to binary.

:-(

This is a bug? Well, there is code that checks the stream for "isBinary" to then use appropriate buffers, i.e. String or ByteArray. 

Best,

Marcel