-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP2 Unsupported #1074
Comments
Hi, Is there an updated ETA on this at all? |
Sorry, the beta for HTTP/2 didn't work out. I'm going to find an alternative solution to support HTTP/2. ETA could be Q2 this year @leearmstrong 😿 |
I also need uses HTTP2. Hope to support it soon |
Yes, this is becoming more and more common! I wonder if a workaround is for Proxyman to force downgrade from HTTP2 to HTTP to at least see the traffic. The ideal thought is for us to see the lot. From memory Charles Proxy allows you to see HTTP2 traffic so it is possible |
I ran into the http2 -> http1.1 forced downgrade today as well. I confirmed my issue that I was trying to debug, but was a bit surprised to realize it was happening. Please add full support for http2, including on image downloads and the like. |
I am unable to use Proxyman until the HTTP2 update arrives. I am looking forward to it. |
Thanks. I understand how important HTTP/2 is. I'm continuing to work on it 👍 |
Friendly reminder: @brr53 @derekmurawsky @leearmstrong @revolyw HTTP/2 is finally implemented. If you don't mind, please check out this Beta build on this comment 👍 : #416 (comment) |
Oh, fantastic! I will try to test this out this week. Thanks! |
I was excited so I tested it out today. Worked for my use case! Thanks, this is awesome! |
Hello, I saw a few months ago someone suggested HTTP2 support and it was shared that it would be released in a few weeks. Just wanted to check in to see if that is still being planned to be released anytime soon.
My application uses HTTP2 and I would like to be able to properly debug it without downgrading connection to HTTP1.1.
Thank you!
The text was updated successfully, but these errors were encountered: