Followup from this problem https://stackoverflow.com/questions/45768893/git-clone-in-windows-much-slower-than-in-linux/45893258#45893258
Windows 10 HTTPS traffic is capped about 200-240kb/s. HTTP traffic can easily reach 8mb/s
This is the same via cabled ethernet or wifi. It is also the same if I plug my PC directly into my HFC cable outlet with no router or firewall.
I have tried another Windows 10 PC with the same issue (same Windows install).
What could cause HTTPS to be 40x slower than HTTP in Windows 10?
I am running Microsoft Windows [Version 10.0.15063] x64 Enterprise
If I run a Kali linux VM in my windows host using a bridge network connection I can obtain 8mb/s via HTTPS. If I set the Kali linux VM to NAT then the speed drops to 200kb/s
If I run a Windows XP VM in my Windows 10 host I get 200kb/s from HTTPS regardless of NAT or Bridged.
edit: I forced my MTU to 576 and confirmed with the following wireshark dump to bitbucket. Speed still ~200kb/s
Frame 147: 590 bytes on wire (4720 bits), 590 bytes captured (4720 bits) on interface 0
Ethernet II, Src: JuniperN_28:63:ca (d4:04:ff:28:63:ca), Dst: Giga-Byt_3c:b0:19 (90:2b:34:3c:b0:19)
Internet Protocol Version 4, Src: 104.192.143.2, Dst: x.x.x.x
Transmission Control Protocol, Src Port: 443, Dst Port: 40796, Seq: 10142, Ack: 528, Len: 536
Source Port: 443
Destination Port: 40796
**[TCP Segment Len: 536]**
0101 .... = Header Length: 20 bytes (5)
Flags: 0x010 (ACK)
Window size value: 30552
[Calculated window size: 30552]
[Window size scaling factor: -2 (no window scaling used)]
Urgent pointer: 0
[SEQ/ACK analysis]
**TCP payload (536 bytes)**
[Reassembled PDU in frame: 152]
**TCP segment data (536 bytes)**
edit: Tried the following netsh int ipv4 reset netsh winsock reset reboot.
Found that IpV6 enabled HTTPS is faster at 3.5mb/s, ipv4 HTTPS is only ~200kb/s
Windows 7 laptop I have available can max out HTTPS at 8mb/s Both windows 10 machines only get ~200kb/s download via HTTPS
Tried disabling firewall, no router etc.