Cloudflare 砍掉 93% TLS 握手往返
推荐指数 66.0 NO. 013 · 2026.09.15
发布2026/09/14Score58Comments16
为什么值得看
Cloudflare 推出自动密钥交换（AKE），通过自适应选择密钥协商算法，将 TLS 1.3 回退请求从 52% 降至 3.7%。对每天 450 亿次源站连接，这意味着平均握手延迟直接减半，且已默认启用后量子加密。
编辑判断
这个优化的巧妙之处在于把"客户端先盲猜算法"这个 TLS 1.3 协议层面的设计缺陷，用服务端预学习和快速探测给补上了。之前行业默认 X25519 是因为兼容性好，但大量源站其实支持更优的 P-256 或 ML-KEM，只是客户端不知道。
对做高并发网关、CDN 或边缘节点的团队有直接参考价值：如果你的服务也需要同时对接大量异构后端，类似的"连接前画像+自适应协商"思路可以复用。另外这是大规模生产环境首次默认启用混合后量子密钥交换，观察其性能数据和回退率变化，对准备迁移 PQ 加密的团队是难得的实测样本。
社区反馈
意见分歧 15 条评论
核心争论：Cloudflare 技术优化是否值得，还是加剧了互联网中心化和用户体验恶化
We had a probe that checked whether a connection was using post-quantum cryptography. It looked for "Cipher is" in the output. But when the handshake failed, it would print "Cipher is (NONE)." So it reported that github.com and amazon.com were compliant. For weeks. The success criterion was embedded
Genuine question: why wouldn’t they have been doing this already? It feels like obvious low-hanging fruit on a critical path, so I presume there’s something more to it than I’m imagining.
TLDR; 1. The TLS handshake involves a step to discover the commonly supported algorithms and can incur additional roundtrip if the first guess does not works out, its part of the protocol to keep it stateless 2. Cloudflare is scanning all the origins on daily basis and storing the result for support