Yep. Honestly I probably would have assumed it's not a protocol issue if both HTTP and HTTPS downloads from S3 behaved the same way. Both of those protocols are on TCP, though, so that would have thrown me off!