I'd say do it the other way around, provide this, and not `getBodyAsStream`, since that implies that you're able to consume the body as an actual stream, not something in memory, when what we get back from the client is not a stream, it's a byte array, and this method just wraps it in a stream.  To force users to go through a stream would result in at least 3 copies of the byte array.

If the user wants a stream, then they need to use an async IO API, (eg an enumerator), and because of the way the underlying client (which is true for all clients I've seen) works, whether they want to handle it as a stream or not needs to be decided up front.  Either you handle it in memory and the http client efficiently consumes it into memory for you, or you use a different method, currently this is `get(WSResponse => Iteratee)`, and then you handle it using an async streaming API.