rethink-app
rethink-app copied to clipboard
HTTP proxy(orbot) is not an http Proxy
Then, I activated Orbot integration inside your app. Rethink said all traffic is now routed over Tor.
The problem is all other apps! can connect to internet, not just Browser if HTTP proxy is enabled (orbot activated) Firewall is completely unusable.
When I disable orbot link, rethink block app's internet connection as advertised.
conclusion: if the HTTP proxy(orbot) is active, your app is ignoring firewall rules silently
#313 @strongok Couldn't answer on parent issue. Image says more than thousand words.
Yes, we merely set it #44, and Android implements the rest (which is a HTTP CONNECT
tunnel instead of a HTTP proxy).
http/1.1 proxies are trivial to implement; it is http/2 that is problematic here: https://github.com/celzero/rethink-app/issues/45#issuecomment-695347020
Ref impl: https://archive.is/etF2f
it is http/2 that is problematic here: https://github.com/celzero/rethink-app/issues/45#issuecomment-695347020
That may not work for any pinned certificates anyway. But it's not needed, The http tunnel port works fine for https and as https proxy. As far I know, Https over http proxy uses http connect.
http/1.1 proxies are trivial to implement;
Previously orbot shipped with polipo http proxy with socks5 as it's parent proxy.
This option causes likely all apps including system Chrome Browser that try to access http to fail:
While TCP forward mode works as expected.
The combinations or use as http proxy works for everything than http itself.
Chrome does not understand to use it as not native http proxy. The way out is set actually
https://github.com/elazarl/goproxy to rescue. Attempting an impl...
Edit: Impl here https://github.com/celzero/firestack/commit/7734c4508f15d6b10f2c0b55efccb542ea34a2f0
https://github.com/elazarl/goproxy to rescue. Attempting an impl...
Good choice. I checked out https://github.com/elazarl/goproxy as HTTP/S=>SOCKS5 Upstream standalone, and it works quite well for this purpose.
I guess since 7734c45 this issue could be closed?
I guess since
7734c45
this issue could be closed?
We haven't integrated it in the app... (:
In v055
, we implement just the HTTP/S CONNECT tunnel and not HTTP/S Proxy per se. Please test it out and let us know if it works as intended; feel free to reopen if it doesn't. Thanks (: