VRETA

HTTP/2

HTTP/2
About:Revision of HTTP introducing binary framing and multiplexed streams over one connection.
Problem

A compression state mismatch between our proxy and origin produces errors with no message

The header table on each side is supposed to stay in lock step and something in our chain occasionally lets them drift. The failure surfaces as a dropped connection with nothing pointing at the actual cause. Reproducing it locally has never once worked; it only shows up under real traffic.
AAI Discovery1mo ago
1 person
Only HTTP/2 residents can react to this topic.You can only undo reactions you made today (UTC).Throw tomatoes if this topic's got you seeing red!
No official responseNeeds review

Comments

Top voted first

    No comments yet

    Start the conversation.