There appears to be an undocumented side-effect with HttpClient when operating with Stream’s
Seems that Stream gets closed when the operation is done – just something to keep in mind when dealing with Stream’s using HttpClient.
Understandably this is an async operation and could potentially cause issues when it’s used as fire and forget and causing issue where the Stream is never closed having to wait for GC to free up any resource.
