https延迟TIME_WAIT连接

从我的客户端PC连接到networking服务器，它只使用HTTPS。

当我连接时，我看到在TCPView（sysinternals工具替代netstat）很多TIME_WAIT连接到https端点。 很多时候我在TIME_WAIT看到11个连接持续2分钟。 这是每次我做一个请求。 2-4连接保持打开ESTABLISHED不pipe多久我设置服务器的Keep-Alive: timeout=xx

后面的连接是可以的，它们被适当的重用。 前连接build立并采取全部2分钟。

我使用WireShark捕获stream量，并在延迟连接的源端口上看到正常的FIN，ACK等。 我经常看到Chrome和IE（它们都使用Windows HTTP协议栈），在任何带有真实数据的请求出现之前发出6个TCP请求。 有效载荷很小（约2000字节）。

• Redis连接问题
• Siege：描述符表full sock.c：119：打开的文件过多
• SQL Server 2008中的证书
• tcptrack显示SYN_SENT连接，这是否意味着SYN包到达服务器？
• 绑定2个或更多的Gigabyte网卡，在1个服务器和1个客户端之间获得2Gbps的性能？

Firefox根本不会发出这些请求…

还值得一提的是，证书是自签名的，并不在浏览器中进行validation（Firefox的处理方式完全不同于Chrome）。

为什么我的浏览器发出这些请求？ 为什么Firefox不能发出这些tcp连接？

编辑，这是从Chrome的第一个连接转储（用wireshark捕获）：

  "https","0.000000",local-ip,dest-ip,"443","TCP","53890 > https [SYN] Seq=0 Win=8192 Len=0 MSS=1460 WS=8 SACK_PERM=1" "53890","0.012749",dest-ip,local-ip,"53890","TCP","https > 53890 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1400 WS=1 SACK_PERM=1" "https","0.012828",local-ip,dest-ip,"443","TCP","53890 > https [ACK] Seq=1 Ack=1 Win=65792 Len=0" "53890","0.025979",dest-ip,local-ip,"53890","TCP","https > 53890 [ACK] Seq=1 Ack=222 Win=128578 Len=0" "53890","0.026099",dest-ip,local-ip,"53890","TLSv1.1","Server Hello, Certificate, Server Hello Done" "53890","0.038848",dest-ip,local-ip,"53890","TCP","https > 53890 [ACK] Seq=1093 Ack=436 Win=128364 Len=0" "53890","0.040474",dest-ip,local-ip,"53890","TLSv1.1","Change Cipher Spec, Encrypted Handshake Message" "https","0.041191",local-ip,dest-ip,"443","TCP","53890 > https [FIN, ACK] Seq=436 Ack=1168 Win=64512 Len=0" "53890","0.053312",dest-ip,local-ip,"53890","TCP","https > 53890 [ACK] Seq=1168 Ack=437 Win=128364 Len=0" "53890","0.053313",dest-ip,local-ip,"53890","TCP","https > 53890 [FIN, PSH, ACK] Seq=1168 Ack=437 Win=128364 Len=0" "https","0.053345",local-ip,dest-ip,"443","TCP","53890 > https [ACK] Seq=437 Ack=1169 Win=64512 Len=0"