TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Observing HTTP/2 Traffic Is Hard, but eBPF Can Help

91 点作者 nserrino超过 3 年前

3 条评论

codetrotter超过 3 年前
On my team we use mitmproxy for observing traffic of our locally running instances of the backend for the project that I am working on.<p>Supposedly mitmproxy also supports HTTP&#x2F;2 so might be helpful for that as well.<p>We&#x27;re personally still using HTTP&#x2F;1.1. But mitmproxy has been a really great tool for us while working on the client and the backend of our project.<p>One thing I also like a lot about mitmproxy is that you can edit requests and replay them. This is useful when I need to step debug the backend for an endpoint where requests are failing or otherwise misbehaving.
staticassertion超过 3 年前
RFC for HPAC here. <a href="https:&#x2F;&#x2F;datatracker.ietf.org&#x2F;doc&#x2F;html&#x2F;rfc7541" rel="nofollow">https:&#x2F;&#x2F;datatracker.ietf.org&#x2F;doc&#x2F;html&#x2F;rfc7541</a><p>A shared client-server compression state is really weird. Can someone explain why this approach was chosen? I&#x27;m assuming that the idea here is to ensure efficiency for short strings by essentially keeping a synchronized dictionary?
评论 #30156749 未加载
mikewang超过 3 年前
any more detailes about this?