Skip to content

Proxy leaks, no autostart, proxy menu UI #555

Description

@embeddedtofu

Internal connections to addons.mozilla.org and icons.duckduckgo.com and the like are not proxied. (Tested with Socks5 and TOR on stable and 0.30 a1 on Android 15/16) For nstance, there's a connection to content-signature-2.cdn.mozilla.net at startup before any proxy can be enabled.

Moreover, DNS requests for example.org, cloudflare-dns.com, and ipv4only.arpa are sent to the system.

DoH is off.


It is also extremely annoying that you have enable the proxy every time you start the app, which can be quite often on a smartphone.

Finally, the proxy UI. I'm not sure about the stats, but if anyone adds a proxy, do they usually configure multiple ones at once?
That is, do we need a drop-down menu for a single proxy? Especially for TOR where you might want request a new exit fairly frequently? It takes up space and adds clicks (opening and closing).

What's more, you can't access proxy routing through that menu, but wouldn't you want to autostart proxies for your containers and keep them enabled anyway?

So, my focus of the design would be to make it more convenient to switch between proxies for global and private tabs.

Thanks in advance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions