Http2 Support using hpack & hyperframe #11522

Vizonex · 2025-09-17T22:49:24Z

What do these changes do?

Many users have begged for http2 protocols and website use http2 to talk to legitimate users. With the rise of this new technologies hosting with http/2 as well as webscraping or using http2 with apis is now in demand. This is a concept for http2 support using hpack & hyperframe.

With httpx supporting http2 protocols already were behind and could use a little bit of the newer protocols ourselves.

I am requesting some assistance with figuring things out including injection of http2 for different kinds of requests or clients that are requesting http/2. (Hence why this is still a draft)

Are there changes in behavior for the user?

HTTP/2 will be added in and allow users to communicate with servers that have http/2 support.

Is it a substantial burden for the maintainers to support this?

The only burden I see is when we start to introduce more things and I have talked heavily on matrix about finding and hunting C libraries or making our own and yes have one already made one for parsing frames :) but we first need a pure python concept before we can use this llh2 library I came up with and more so the pure python stuff is what we will focus on tackling first.

Related issue number

Checklist

I think the code is well written
Unit tests for the changes exist
Documentation reflects the changes
If you provide code modification, please add yourself to CONTRIBUTORS.txt
- The format is <Name> <Surname>.
- Please keep alphabetical order, the file is sorted by names.
Add a new news fragment into the CHANGES/ folder
- name it <issue_or_pr_num>.<type>.rst (e.g. 588.bugfix.rst)
- if you don't have an issue number, change it to the pull request
  number after creating the PR
  - .bugfix: A bug fix for something the maintainers deemed an
    improper undesired behavior that got corrected to match
    pre-agreed expectations.
  - .feature: A new behavior, public APIs. That sort of stuff.
  - .deprecation: A declaration of future API removals and breaking
    changes in behavior.
  - .breaking: When something public is removed in a breaking way.
    Could be deprecated in an earlier release.
  - .doc: Notable updates to the documentation structure or build
    process.
  - .packaging: Notes for downstreams about unobvious side effects
    and tooling. Changes in the test invocation considerations and
    runtime assumptions.
  - .contrib: Stuff that affects the contributor experience. e.g.
    Running tests, building the docs, setting up the development
    environment.
  - .misc: Changes that are hard to assign to any of the above
    categories.
- Make sure to use full sentences with correct case and punctuation,
  for example:
```
Fixed issue with non-ascii contents in doctest text files
-- by :user:`contributor-gh-handle`.
```
  Use the past tense or the present tense a non-imperative mood,
  referring to what's changed compared to the last released version
  of this project.

for more information, see https://pre-commit.ci

aiohttp/http2_parser.py

@@ -0,0 +1,192 @@
+import base64  # TODO: Pybase64 or libbase64 in Cython would be a good idea here...


aiohttp/http2_parser.py

+from hpack.hpack import Decoder
+from http_writer import HttpVersion, HttpVersion20
+from hyperframe.frame import ContinuationFrame, Frame, GoAwayFrame, HeadersFrame
+from multidict import CIMultiDict, CIMultiDictProxy, istr


aiohttp/http2_parser.py

+from multidict import CIMultiDict, CIMultiDictProxy, istr
+from yarl import URL
+
+from . import hdrs


aiohttp/http2_parser.py

+    BrotliDecompressor,
+    ZLibDecompressor,
+    ZSTDDecompressor,
+)
+from .http_parser import RawRequestMessage, RawResponseMessage, _MsgT
+from .streams import EMPTY_PAYLOAD, StreamReader
+from .typedefs import RawHeaders


aiohttp/http2_parser.py

+    ZSTDDecompressor,
+)
+from .http_parser import RawRequestMessage, RawResponseMessage, _MsgT
+from .streams import EMPTY_PAYLOAD, StreamReader


aiohttp/http2_parser.py

+)
+from .http_parser import RawRequestMessage, RawResponseMessage, _MsgT
+from .streams import EMPTY_PAYLOAD, StreamReader
+from .typedefs import RawHeaders


aiohttp/http2_writer.py

+
+# Reflects h2/connection from a lower-level prespective so
+# socket writing can be a bit more optimized.
+from hpack.hpack import Decoder, Encoder


aiohttp/http2_writer.py

+from .base_protocol import BaseProtocol
+from .client_exceptions import ClientConnectionResetError
+from .compression_utils import ZLibCompressor
+from .helpers import NO_EXTENSIONS


codspeed-hq · 2025-09-17T22:59:22Z

CodSpeed Performance Report

Merging #11522 will not alter performance

_{Comparing Vizonex:http2 (f89c153) with master (230e1ee)}

Summary

✅ 59 untouched

Dreamsorcerer · 2025-09-19T14:44:43Z

We probably need some tests (and it actually being linked together to the rest of the project) showing the implementation working before we review this.

Vizonex · 2025-09-19T15:46:26Z

We probably need some tests (and it actually being linked together to the rest of the project) showing the implementation working before we review this.

Sure thing ^^ This is a draft after all and I will need help and suggestions in the matrix if I need it I want to create a dynamic setup when swapping from http/1.1 to http/2 before I start the PR. I thought about writing a abstract class object for the transitioning with all the inner stuff like sockets and things but let me see about making that and finding a dummy server that has http2 before I begin.

Dreamsorcerer · 2025-09-19T17:17:55Z

Also, isn't h2 meant to handle most of this? I'm wondering if you've not just started recreating h2..

Vizonex and others added 3 commits September 17, 2025 17:38

Create http2_parser.py

7d82af1

Create http2_writer.py

69d3f16

[pre-commit.ci] auto fixes from pre-commit.com hooks

f89c153

for more information, see https://pre-commit.ci

github-advanced-security bot found potential problems Sep 17, 2025

View reviewed changes

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

Http2 Support using hpack & hyperframe #11522

Http2 Support using hpack & hyperframe #11522

Vizonex commented Sep 17, 2025

Uh oh!

Check notice

Check notice

Check notice

Check notice

Check notice

Check notice

Check notice

Check notice

codspeed-hq bot commented Sep 17, 2025

Uh oh!

Dreamsorcerer commented Sep 19, 2025 •

edited

Loading

Uh oh!

Vizonex commented Sep 19, 2025 •

edited

Loading

Uh oh!

Dreamsorcerer commented Sep 19, 2025

Uh oh!

Uh oh!

		@@ -0,0 +1,192 @@
		import base64 # TODO: Pybase64 or libbase64 in Cython would be a good idea here...

Uh oh!

Http2 Support using hpack & hyperframe #11522

Are you sure you want to change the base?

Http2 Support using hpack & hyperframe #11522

Conversation

Vizonex commented Sep 17, 2025

What do these changes do?

Are there changes in behavior for the user?

Is it a substantial burden for the maintainers to support this?

Related issue number

Checklist

Uh oh!

Check notice

Check notice

Check notice

Check notice

Check notice

Check notice

Check notice

Check notice

codspeed-hq bot commented Sep 17, 2025

CodSpeed Performance Report

Merging #11522 will not alter performance

Summary

Uh oh!

Dreamsorcerer commented Sep 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Vizonex commented Sep 19, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Dreamsorcerer commented Sep 19, 2025

Uh oh!

Uh oh!

Dreamsorcerer commented Sep 19, 2025 •

edited

Loading

Vizonex commented Sep 19, 2025 •

edited

Loading