HTTPSE toggle not working correctly

[LaurenWags]

Description

If you're on a site (like https://https-everywhere.badssl.com/) and you toggle HTTPSE off from shields, page still shows that HTTPSE is enabled even if you refresh the page.

This does not reproduce on 1.5.123.

Steps to Reproduce

1. Clean profile 1.7.86.
2. Navigate to https://https-everywhere.badssl.com/
3. Open shields, disable HTTPSE.

Same thing happens on a profile upgraded from 1.5.123.

Actual result:

Page still says HTTPSE is working (same thing happens even if you refresh the page.

Expected result:

Page should indicate that HTTPSE is not working or not enabled as it does on 1.5.123:

Reproduces how often:

easily

Brave version (brave://version info)

Brave	1.7.86 Chromium: 80.0.3987.163 (Official Build) (64-bit)
Revision	e7fbe071abe9328cdce4ffedac9822435fbd3656-refs/branch-heads/3987@{#1037}
OS	macOS Version 10.14.6 (Build 18G3020)

Version/Channel Information:

• Can you reproduce this issue with the current release? does not reproduce on 1.5.123
• Can you reproduce this issue with the beta channel? yes
• Can you reproduce this issue with the dev channel? yes
• Can you reproduce this issue with the nightly channel? yes

Other Additional Information:

• Does the issue resolve itself when disabling Brave Shields?
• Does the issue resolve itself when disabling Brave Rewards?
• Is the issue reproducible on the latest version of Chrome?

Miscellaneous Information:

cc @rebron @brave/legacy_qa

[btlechowski]

Reproduced on Linux

Brave	1.7.86 Chromium: 80.0.3987.163 (Official Build) (64-bit)
Revision	e7fbe071abe9328cdce4ffedac9822435fbd3656-refs/branch-heads/3987@{#1037}
OS	Ubuntu 18.04 LTS

[bsclifton]

There is a regression with the website itself - which happened starting with brave/brave-core#4537

However- the functionality is working as expected 😄 Thanks to @fmarier for the following test plan, which I also ran through and verified

I tested it successfully in Beta like this:

1. Open http://https-everywhere.badssl.com/ (you then get redirected to https://https-everywhere.badssl.com/).
2. Open shields, disable HTTPSE.
3. Open http://https-everywhere.badssl.com/ (you do not redirected).

I believe we should close this as expected behavior