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.
Known issue: Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them. #19029
Update to Release 2020.3.16 with new feature that allows manually whitelisting hosts seems to break whitelisting for few URLs that I'm using.
For example, if I have EASE enabled when I visit URL like http://abcd.local:4000 (which points to something along the lines of 127.x.y.z in my hosts file), I see the HTTPS Everywhere noticed you were navigating to a non-HTTPS page, even though I had whitelisted it in previous versions by pressing "open insecure page". Looking at the list of hosts I see an entry for abcd.local:4000 in there but it doesn't seem to be doing anything. Deleting it doesn't change anything, re-adding it also seems to have no effect.
Neither pressing "open insecure page" nor pressing "open insecure page for this session only" nor manually whitelisting it seems to work, so it seems that the only currently available workaround is to disable EASE.
changed the title [-]Release 2020.3.16 breaks whitelisting of some pages and "open insecure page" for them.[/-][+]Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them.[/+]on Mar 17, 2020
Installing the previous 2019.11.7 fixes this issue for me. I do not know if auto updates will work in the future, or if this work around will have to regularly reapplied due to auto updates.
Another option is to turn off EASE (Encrypt All Sites Eligible), but if you have that turned on, likely you do for a very valid reason, and disabling that is likely worse than downgrading.
P.S. @zoracon I'd recommend leaving this issue open until a release is pushed so that people can find these solutions instead of creating new issues. It was very easy to find when it was open since it was recent and near the top, but now that it's closed, it will be harder for people to find the solutions.
Thank you for reacting fast, fixing the issue and providing a workaround.
@ivan-kolmychek Thank you for reporting concisely. The shelter-in-place order was rolled out while this release was being made. I really appreciate the understanding.
Due to the fact this discussion is not realistically able to make the shelter-in-place order go away, I am locking this issue. @zoracon please reverse if appropriate.
changed the title [-]Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them.[/-][+]Known issue: Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them.[/+]on Mar 30, 2020
Activity
[-]Release 2020.3.16 breaks whitelisting of some pages and "open insecure page" for them.[/-][+]Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them.[/+]ivan-kolmychek commentedon Mar 17, 2020
Forgot to mention that it all is happening in Chromium 80.0.3987.132.
cschanaj commentedon Mar 17, 2020
#18760 introduced a regression for the whitelisting features, I have just filed a fix #19032.
jmgurney commentedon Mar 18, 2020
And there appears to be no plans to do a release for a couple weeks:
#19032 (comment)
pipboy96 commentedon Mar 18, 2020
@jmgurney You may thank COVID-19 for that.
jmgurney commentedon Mar 18, 2020
Thanks to @zoracon for providing a work around for this issue:
#19032 (comment)
Installing the previous 2019.11.7 fixes this issue for me. I do not know if auto updates will work in the future, or if this work around will have to regularly reapplied due to auto updates.
Resolve a regression which breaks whitelisting features, fix #19029 (#…
jmgurney commentedon Mar 18, 2020
Another option is to turn off EASE (Encrypt All Sites Eligible), but if you have that turned on, likely you do for a very valid reason, and disabling that is likely worse than downgrading.
#19032 (comment)
P.S. @zoracon I'd recommend leaving this issue open until a release is pushed so that people can find these solutions instead of creating new issues. It was very easy to find when it was open since it was recent and near the top, but now that it's closed, it will be harder for people to find the solutions.
ivan-kolmychek commentedon Mar 23, 2020
Thank you for reacting fast, fixing the issue and providing a workaround.
Given the circumstances I think its totally understandable that release cannot be cut right now.
zoracon commentedon Mar 23, 2020
@ivan-kolmychek Thank you for reporting concisely. The shelter-in-place order was rolled out while this release was being made. I really appreciate the understanding.
pipboy96 commentedon Mar 23, 2020
Due to the fact this discussion is not realistically able to make the shelter-in-place order go away, I am locking this issue. @zoracon please reverse if appropriate.
[-]Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them.[/-][+]Known issue: Release 2020.3.16 breaks whitelisting of some URLS and "open insecure page" button for them.[/+]zoracon commentedon May 21, 2020
Resolved with #19288
Revert #19029 and #18760 (#19292)