Closed boredsquirrel closed 3 months ago
allow to exclude apps from HTTP block
Excluding the browser from the "universal" blocking didnt work.
You mean Bypass Universal did not work (as in bypass the block HTTP on port 80 universal firewall rule)? That's a bug.
If so, after the browser apps have been Bypass Universal:
I used Mull and tried to open httpforever.com
I had the "block HTTP" as my only rule of that category.
The "Bypass Universal" still didnt allow me to open the HTTP site, while turning the rule off entirely did.
strange, could not reproduce.
Previously, I think:
Now I have the same but also use a local filterlist, while using Quad9 DNSCrypt. And cant reproduce currently.
Thanks. Seems like it was a one-off.
For next time, check Network Log entries for Mull (or any other app you suspect isn't working as expected) for why its connection don't worke (either firewalled or simply failed). When you tap on the entries shown in Network Log, a bottomsheet with more information about the connection should show up. For finished connections (connections not currently ongoing / active), the footer of the bottomsheet shows diagnostic messages (final status of the connections).
Browsers can block HTTP themselves but allow opt-in with a warning.
This is way better UX than needing to manually allowlist a website.
Excluding the browser from the "universal" blocking didnt work.