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.

No provision for NON-HTTPS connection on LAN such as for router maintenance #13511

Closed

Description

@Jimbazuka

Type: ruleset issue
Type: other

if "block all unencrypted requests" is set - you can not create a rule to connect to
a LAN address such as 192.168.1.1 (for router maintenance etc.) - there is no way to
make a rule (or none I could figure) for such a case. If you uncheck "block all unencrypted requests"
you may encounter unwanted issues such as redirecting to http when you wanted https

Activity

  1. https-everywhere-bot commented on Nov 7, 2017

    @https-everywhere-bot

    Hello! You seem to have specified more than one type. Can you edit your issue and delete all but one of the types in your issue?

  2. jeremyn commented on Nov 7, 2017

    @jeremyn
    Contributor

    @Jimbazuka Thanks for your report, but I'm closing this issue as a duplicate of issue #2323, particularly the whitelist comment in #2323 (comment). Please feel free to add comments to that issue if you like. See also issue #9142.

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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions