HPACK
E40363
HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
All labels observed (5)
| Label | Occurrences |
|---|---|
| HPACK canonical | 7 |
| HPACK: Header Compression for HTTP/2 | 3 |
| HTTP/2 HPACK header compression specification | 1 |
| IANA HPACK static table registry | 1 |
| Internet Standard for HTTP/2 header compression | 1 |
How this entity was disambiguated
This entity first appeared as the object of triple T306765 — resolving that mention is where its identity was fixed. The disambiguator weighed these candidate entities and picked the highlighted one (or “None”, minting a new entity). This is how homonymy is resolved: the same surface form can point to different entities.
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: HPACK Context triple: [HTTP/2, headerCompressionAlgorithm, HPACK]
-
A.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
B.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
C.
QUIC
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
-
D.
SPDY
SPDY is an experimental, now-deprecated web protocol developed by Google to speed up and secure HTTP traffic, which heavily influenced the design of HTTP/2.
-
E.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: HPACK Target entity description: HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
-
A.
HTTP/2
HTTP/2 is a major revision of the Hypertext Transfer Protocol that introduced features like multiplexing, header compression, and server push to significantly improve web performance over HTTP/1.1.
-
B.
HTTP/3
HTTP/3 is the third major version of the Hypertext Transfer Protocol, built on the QUIC transport protocol to provide faster, more reliable, and secure web communication.
-
C.
QUIC
QUIC is a modern, multiplexed transport protocol developed by Google and standardized by the IETF that runs over UDP to provide faster, more secure, and reliable web connections than traditional TCP-based HTTPS.
-
D.
SPDY
SPDY is an experimental, now-deprecated web protocol developed by Google to speed up and secure HTTP traffic, which heavily influenced the design of HTTP/2.
-
E.
HTTP
HTTP (Hypertext Transfer Protocol) is the foundational application-layer protocol used for transmitting web pages and other resources across the World Wide Web.
- F. None of above. chosen
Statements (48)
| Predicate | Object |
|---|---|
| instanceOf |
HTTP/2 component
ⓘ
header compression format ⓘ |
| appliesTo |
HTTP header field names
ⓘ
HTTP header field values ⓘ |
| compressionScope |
HTTP request headers
ⓘ
HTTP response headers ⓘ |
| defines |
Huffman code table for header field values
ⓘ
binary encoding for header fields ⓘ static header field table entries ⓘ |
| designedFor |
efficient encoding of HTTP header fields
ⓘ
improving HTTP/2 performance ⓘ mitigating security risks of header compression ⓘ reduction of HTTP header size ⓘ |
| encodingType | binary ⓘ |
| fullName |
HPACK: Header Compression for HTTP/2
ⓘ
linked to:
HPACK
|
| hasGoal |
compression efficiency
ⓘ
deterministic memory use ⓘ low CPU overhead ⓘ protection against compression side‑channel attacks ⓘ |
| hasLimit | configurable maximum dynamic table size ⓘ |
| influencedBy | SPDY header compression ⓘ |
| influences | QPACK header compression for HTTP/3 ⓘ |
| publicationYear | 2015 ⓘ |
| publishedBy |
IETF
ⓘ
linked to:
Internet Engineering Task Force
|
| relatedTo |
HTTP/2
ⓘ
QPACK ⓘ |
| replaces | generic compression of HTTP headers used in HTTP/1.x ⓘ |
| securityProperty |
allows limiting dynamic table size per endpoint
ⓘ
avoids use of general‑purpose stream compression over TLS for headers ⓘ reduces risk of CRIME‑like attacks on HTTP headers ⓘ |
| standardizedIn | RFC 7541 ⓘ |
| status |
Internet Standard for HTTP/2 header compression
ⓘ
linked to:
HPACK
|
| supportsOperation |
header table eviction
ⓘ
header table insertion ⓘ header table resizing ⓘ indexed header field representation ⓘ literal header field never indexed ⓘ literal header field representation ⓘ literal header field with indexing ⓘ literal header field without indexing ⓘ |
| usedByProtocol | HTTP/2 ⓘ |
| usesDataStructure |
dynamic table
ⓘ
static table ⓘ |
| usesTechnique |
dynamic Huffman coding
ⓘ
header table indexing ⓘ indexed representation of header fields ⓘ static Huffman coding ⓘ |
| workingGroup |
IETF HTTPbis Working Group
ⓘ
linked to:
HTTP Working Group
|
How these facts were elicited
The pipeline generated the facts above by prompting gpt-5.1 with this entity's name + description and the instruction below.
Instruction
You are a knowledge base construction expert. Given a subject entity and a description of it, return factual statements that you know for the subject as a JSON list of dictionaries(triples), where keys must be "subject", "predicate" and "object". The number of facts may be very high, between 25 to 50 or more, for very popular subjects. For less popular subjects, the number of facts can be very low, like 5 or 10. # Requirements - If you don't know the subject at all, return an empty list. - If the subject is not a named entity, return an empty list. - Include at least one triple where predicate is "instanceOf". - Do not get too wordy. - Separate several objects into multiple triples with one object.
Input
Subject: HPACK Description of subject: HPACK is the dedicated header compression format used by HTTP/2 to efficiently encode and transmit HTTP header fields while maintaining security and performance.
Referenced by (13)
Full triples — surface form annotated when it differs from this entity's canonical label.
linked to: HPACK
linked to: HPACK