Skip to content
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
This repository was archived by the owner on Nov 6, 2023. It is now read-only.

Exclude all local subnets from HTTPSE #18474

Closed

Description

@Hainish

Type: code issue

Coming in from email:

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.

What do people think about this request?

Activity

  1. pipboy96 commented on Oct 2, 2019

    @pipboy96
    Contributor

    @Hainish The most obvious reason this is needed is to let people configure their routers without disabling EASE.

  2. pipboy96 commented on Oct 2, 2019

    @pipboy96
    Contributor

    Maybe we need to also let the user decide on domain names/IP ranges they want whitelisted from EASE?

  3. zoracon commented on Oct 7, 2019

    @zoracon
    Contributor

    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.

  4. pipboy96 commented on Oct 7, 2019

    @pipboy96
    Contributor

    @zoracon Most common case would be 192.168.(0|1).1 (most routers have a settings page listening on this IP)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions