Firefox、Websockets、HTTP/2 和连接失败
作者: toastal创建于 2025年3月26日更新于 2026年6月13日
The behavior is that Chromium connects fine (101 Connection) after a bit of a connection delay, but Firefox eventually fails out with a 400 and no body. Disabling HTTP/2 on the server via Fx’s about:config with network.http.http2.enabled or network.http.http2.enabled set to false gives the desired 101. Fiddling with the other proxy values doesn’t seem to help (or makes things worse, and Chromium doesn’t connect). Disabling ad blocking + tracking protection in Fx did nothing.
内容来源: h2o/h2o