The HPACK spec [1] remarks on this. Google carefully used DEFLATE in earlier SPDY versions [2] but HTTP&#x2F;2 decided to be less clever.<p>Interestingly, SLZ&#x27;s page comments on lack of history as a way to avoid CRIME attacks, which is one of the things the HTTP&#x2F;2 people worried about. That seems like something it&#x27;d be easy for an implementation to screw up though (just add some buffering somewhere before the compressor...)<p>[1] <a href="https:&#x2F;&#x2F;http2.github.io&#x2F;http2-spec&#x2F;compression.html#rfc.section.1" rel="nofollow">https:&#x2F;&#x2F;http2.github.io&#x2F;http2-spec&#x2F;compression.html#rfc.sect...</a>
[2] <a href="https:&#x2F;&#x2F;www.chromium.org&#x2F;spdy&#x2F;spdy-protocol&#x2F;spdy-protocol-draft3#TOC-2.6.10.1-Compression" rel="nofollow">https:&#x2F;&#x2F;www.chromium.org&#x2F;spdy&#x2F;spdy-protocol&#x2F;spdy-protocol-dr...</a>