So what you're really saying is "no, it doesn't only happen with https"? Shouldn't this fix be at the socket level, rather than the http client level?