Bug 1647033 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.

To reproduce:

1. Set dom.security.https_only_mode to true
2. go to http://neverssl.com

Results:
1. We see an error page for https://neverssl.com/ 
2. After clicking "continue" we then see an error page for https://kbcnhfdlmzrwsvxt.neverssl.com/online
3. After clicking continue a second time, do we arrive at the site.

Expected results:
We should expect to see only one error page

Possible solution: index the https-only-mode whitelist to eTLD+1.
To reproduce:

1. Set dom.security.https_only_mode to true
2. go to http://neverssl.com

Results:
1. We see an error page for https://neverssl.com/ 
2. After clicking "continue" we then see an error page for https://kbcnhfdlmzrwsvxt.neverssl.com/online
3. After clicking "continue" a second time, we see the content of the site.

Expected results:
We should expect to see only one error page

Possible solution: index the https-only-mode whitelist to eTLD+1.
To reproduce:

1. Set dom.security.https_only_mode to true
2. go to http://neverssl.com

Results:
1. We see an error page for https://neverssl.com/ 
2. After clicking "continue" we then see an error page for https://kbcnhfdlmzrwsvxt.neverssl.com/online
3. After clicking "continue" a second time, we see the content of the site.

Expected results:
We should expect to see only one error page.

Possible solution: index the https-only-mode whitelist to eTLD+1.

Back to Bug 1647033 Comment 0