読み込み中...
読み込み中...
RFC 9113・7541・9218に基づき、multiplexing、optional Server Push、HPACK、binary framing、priority、two-level DATA flow controlをexact6で確認できます。
最終更新日 ・ by yuzlrin
| 項目 | 内容 |
|---|---|
| Multiplexing | Multiple concurrently open streams share one connection — Frames from multiple open streams can be interleaved on one HTTP/2 connection; this does not remove TCP-level head-of-line blocking. (RFC 9113 §5) |
| Server Push | Optional PUSH_PROMISE; client can disable with SETTINGS_ENABLE_PUSH=0 — A server can initiate a promised request through PUSH_PROMISE only when push is permitted; client disablement is a protocol setting, not a universal ecosystem deprecation. (RFC 9113 §8.4 / §6.5.2) |
| Field compression | HPACK — HTTP/2 compresses field sections using HPACK as specified by RFC 7541; internal tables and Huffman coding are outside this overview. (RFC 7541 RFC 7541) |
| Binary framing | Fixed 9-octet header plus variable-length payload — Each HTTP/2 frame begins with a fixed 9-octet header followed by a variable-length payload whose structure depends on frame type. (RFC 9113 §4.1) |
| Priority | Deprecated RFC 7540 dependencies; RFC 9218 extensible signals when supported — RFC 9113 deprecates dependency-based priority signaling; RFC 9218 signals apply only with indicated support and do not guarantee scheduling or performance outcomes. (RFC 9113 + RFC 9218 §5.3 / §5.3.2) |
| Flow control | Connection-level and stream-level windows for DATA frames — Both connection and stream flow-control windows constrain DATA frames only; other frame types do not consume these windows. (RFC 9113 §5.2) |