AMAZINGINDEX.COM 每天向上一点
59.4
VOL. 2026.11
2026.11.17
← 返回 2026.11.17 日报
日报快照 · Daily Snapshot
NO. 020

HTTP/3 流量拦截实战指南

#ARTICLE HackerNews 2026.11.17
推荐指数 63.0 NO. 020 · 2026.11.17
发布2026/11/16Score57Comments6

HTTP/3 基于 QUIC/UDP 运行,传统 TCP 代理如 Burp Suite 无法拦截。文章演示了如何搭建支持 UDP 中继和 QUIC 中间人攻击的代理,并解析 QPACK 压缩后的请求字节流。对做安全测试、API 调试和流量分析的工程师有直接参考价值。

HTTP/3 普及速度比很多人预期的快,Cloudflare 和 Google 已经大面积切过去,但安全工具链明显滞后。现在大多数渗透测试和 API 调试工作流还是围绕 HTTP/1.1 和 HTTP/2 设计的,HTTP/3 的流量直接成了盲区。

如果你在用 Burp Suite 或 Charles 做安全审计,需要开始评估 mitmproxy 的 QUIC 支持或者 InterceptSuite 这类新工具,否则未来半年内会遇到越来越多的"抓不到包"情况。另外 QPACK 动态表的状态管理是个坑,同一个请求在不同时间点抓到的字节流可能完全不同,写自动化分析脚本时要特别注意。

意见分歧 6 条评论

核心争论:企业 TLS 中间人检测是否真正有效,还是只会导致回退到 HTTP/2

rbartelme

The key requirement here is the client has to trust the proxy's CA. It's a client-side MITM, and the article itself notes pinned apps reject it. QUIC's crypto is fine. HTTP/3 just stopped being a blind spot for corporate TLS-inspection boxes. It's more interesting to split tunnel designs by whe

9cb14c1ec0

> HTTP/3 just stopped being a blind spot for corporate TLS-inspection boxes. Or alternatively said TSL-inspection boxes just block QUIC and everything auto-fails back over to HTTP/2, just like we've all been doing for years.

LeBit

If my employer puts their CA in the corporate laptop they provide me and I try to access my private web site which uses a letsencrypt cert, the browser will tell me the cert does not match if my employer did mitm attack, no?

替代方案: ngrokCloudflare Tunnel
查看原文 →