Support HTTP/2

[NghiaTranUIT]

🐶 Brief

At the moment, all intercepted HTTP/HTTPS through Proxyman will be downgraded to HTTP/1.1. We should support HTTP/2 too and implement the HTTP/2 parser correctly.

👑 Criteria

• Support h2 ALPN in CocoaAsyncSocket
• Determine whether or not the request is HTTP/2
• Write HTTP/2 Parser. We could inspired from Apple-Server source
• Work with current architecture. HTTP/1.x and HTTP/2

Update 1 (5 Feb 2023): Beta build for HTTP/2 is ready ✅

Comment: #416 (comment)

Update 2 (14 Feb 2023): New Update

Comment: #416 (comment)

Update 3 (22 Feb 2023):

#416 (comment)

The HTTP/2 is finally merged to the latest build - v26.0.0 today 🎉🎉🎉

I'm sorry to keep the HTTP/2 Beta so long. Thanks your patient.

You can directly update from your app or download it at https://github.com/ProxymanApp/Proxyman/releases/tag/26.0.0

[Saklad5]

Any progress on this?

[NghiaTranUIT]

@Saklad5 Sorry, but at the moment, I'm working on Protobuf feature.

When it's done, I will kick start the HTTP/2 since it's crucial to support gRPC feature too 🙌

[Saklad5]

Glad to see the Protobuf feature is done: it’s not something I’m interested in, but it means you might work on this soon.
Once Proxyman can run without downgrading traffic, I think I’ll purchase it. Until then, I can’t really justify running it for long periods of time, which limits its utility.

[NghiaTranUIT]

I would like to say that HTTP/2 and HTTP/3 are must-have features of Proxyman, and the progress is really good at the moment 🙌

Protobuf, the first blocker is done, it's time for HTTP/2.

Stay tuned 🌮

[Saklad5]

HTTP/3 isn’t formally accepted yet, so I’d say that’s less of a must-have than HTTP/2. I generally don’t expect things to support draft standards, and I understand it is pretty different.

By the way, does Proxyman do any other downgrading at the moment? Besides forcing HTTP/1, does simply running it affect outgoing traffic at all?

[NghiaTranUIT]

At the moment, only HTTPS domains, which enable SSL-Proxying (To see the HTTP Response Content) is downgraded to HTTP/1.

Otherwise, HTTPS (no SSL-Proxying) and HTTP are not, since it's just a proxy server, no interception. Thus, it would keep HTTP/2 or other protocols without changing it.

As there are no reliable HTTP/2 servers on macOS (Swift/Objc) yet, so it's the reason why Proxyman doesn't support HTTP/2 at the first implementation. However, Swift-NIO from Apple is fully supported recently, so I'm planning to rewrite the Proxyman Core with NIO stack.

When 1.23.0 build is out this weekend, I will push HTTP/2 forward 👍

[wasder]

Looking forward for gRPC support.
Could be a killer feature, as nothing yet so handy support it.👍

[bbuckland]

@NghiaTranUIT sounds like you've made a ton of progress towards this. Could you share where you're at with HTTP/2, specifically to enable gRPC?

[NghiaTranUIT]

@bbuckland We're migrating the codebase to HTTP/2 but it hasn't finished yet. I will push it forward soon after the Multiple Filters and Diffing is done 🙌

To workaround and see the gRPC data, you might consider using Atlantis from Proxyman (https://github.com/ProxymanApp/atlantis#2-my-app-use-grpc)

[inickt]

Would love to know if there are any updates on this, our backend microservices only talk over HTTP/2 and I would love to use Proxyman + the beta of the reverse proxy feature to improve my backend workflow.

That being said I switched over from Charles this week and it has been amazing for testing iOS things!

[NghiaTranUIT]

Thanks for the upvote @inickt. Since the Reverse Proxy is almost done (we're going to release it in this week), so our team is working on the HTTP/2 👍

We will send a Beta build here when it's available 😄

[inickt]

Hey, I was curious if there have been any updates on this? Still been loving the app so thanks for all of your work and the great updates!

[NghiaTranUIT]

Hey @inickt Thanks for your shoutout.

To be honest, I tried to support HTTP/2 months ago but it doesn't work well since it's a breaking change in our codebase 😿 . The problem is not just supporting HTTP/2, it also includes HTTP/1.1 as backward compatible.

At the moment, I'm focusing on the Folder Rule (where you can organize the tool rules in folders). When it's done, I will back to HTTP/2 👍