InlineKnowledgeCheck({
containerId: "kc-http2-hpack-inline",
question: "After the first HTTP/2 request sends full headers (~350 bytes), what does HPACK send for the same headers on subsequent requests to the same server?",
options: [
"~15-30 bytes of index references into the shared header table",
"The same ~350 bytes, because headers must be re-validated each time",
"Zero bytes, because the server caches all headers permanently",
"~175 bytes, because HPACK compresses headers by exactly 50%"
],
correctIndex: 0,
explanation: "HPACK builds a shared header table indexed between client and server. After the first request populates the table, subsequent requests with the same headers (Host, Authorization, Content-Type, etc.) send only small integer index references — typically 15-30 bytes — instead of retransmitting the full header strings. This 90%+ reduction is especially valuable for IoT devices that repeat the same headers on every reading upload.",
difficulty: "intermediate"
})