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 was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Hello,
I would like to know if HTTPS everywhere can be disabled globally for private ip addresses (10.0.0.0/8 172.16.0.0/12 192.168.0.0/16) since they don't need https most of the time being
in the same subnet and it would be very inconvenient to disable HTTPS everywhere for every single ip address.
Still deciding on whether this is a common enough use case to implement, right now if the user is on a private net, is using public facing applications common? Maybe I'm thinking of older intranet infrastructure.
Activity
pipboy96 commentedon Oct 2, 2019
@Hainish The most obvious reason this is needed is to let people configure their routers without disabling EASE.
pipboy96 commentedon Oct 2, 2019
Maybe we need to also let the user decide on domain names/IP ranges they want whitelisted from EASE?
zoracon commentedon Oct 7, 2019
Still deciding on whether this is a common enough use case to implement, right now if the user is on a private net, is using public facing applications common? Maybe I'm thinking of older intranet infrastructure.
pipboy96 commentedon Oct 7, 2019
@zoracon Most common case would be 192.168.(0|1).1 (most routers have a settings page listening on this IP)