You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 9, 2023. It is now read-only.
The "simple" way.:
Create a proxy (HTTP2 Enabled) that checks on connect, what the requested HTTP protocol version is, if the requested protocol is 1.1 Exact (meaning the client won't accept an upgrade to HTTP2), forward to a second proxy that has HTTP2Enabled on false (If i remember right, theres a func property for that - CustomUpstreamProxySelect or something like that.
Beside that, I would strongly suggest leaving HTTP2 off, because its restricting you still due to the implementation in this proxy API, due to not (yet) 100% implemented. What exactly are u trying to achieve? The only thing where the protocol change would affect you, is during decryption - you could use a HTTP1.1 conneciton in 99,999% of the target hosts, i barely met any host that did exclude 1.1, and 1.1 is still a standardized protocol, not being deprecated - and still lots of appliances etc. even new ones rely on it - and with HTTP3.0 still being not final and with a timespan of years to expect until it being also counting standard, theres no danger of 1.1 being deprecated anytime soon.
I assume, you're having a client application/appliance or some sort of office/corporate policy enforcing HTTP2? Or - the only other thing I can imagine, you're having issues trying to deal with ReCaptcha while decrypting? :P
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
titanium-web-proxy/src/Titanium.Web.Proxy/ExplicitClientHandler.cs
Line 145 in 1e9d602
It seems that currently, it doesn't support both protocol at the same time, any workaround or any plan for supporting this?
The text was updated successfully, but these errors were encountered: