STR: 1. Enable the Trust Panel and enable HTTPS-Only 2. if necessary, clear any HTTPS-only exceptions from the test sites 2a. click on link to http://http.rip (http link to http-only site) 2b. click on link to https://scripting.com (https link that redirects to http-only site) Expected Result: The "**HTTPS-Only Mode Alert**" page appears immediately with the ability to "continue to http" or "go back" Actual Result: Nothing except a little hover text at the bottom saying "connecting to http.rip". If you do nothing and wait for the timeout (over a minute, maybe two?) eventually the alert page will show. In practice completely unusable: will appear to be a broken link as far as any user could tell. This is not yet enabled by default, but it would be a regression from the pref-flip bug 1988726 when that lands. Not sure which dependency of bug 1964725 actually did this, though.
Bug 1997169 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
STR: 1. Enable the Trust Panel and enable HTTPS-Only 2. if necessary, clear any HTTPS-only exceptions from the test sites 2a. click on link to http://http.rip (http link to http-only site) 2b. click on link to https://http.badssl.com (https link that redirects to http-only site) Expected Result: The "**HTTPS-Only Mode Alert**" page appears immediately with the ability to "continue to http" or "go back" Actual Result: Nothing except a little hover text at the bottom saying "connecting to http.rip". If you do nothing and wait for the timeout (over a minute, maybe two?) eventually the alert page will show. In practice completely unusable: will appear to be a broken link as far as any user could tell. This is not yet enabled by default, but it would be a regression from the pref-flip bug 1988726 when that lands. Not sure which dependency of bug 1964725 actually did this, though. [updated STR 2b to a similar site to fix a broken link]