Bug 2021712 Comment 1 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Test page: https://tls-v1-1.badssl.com:1011/ 
Firefox 149 Beta Secure Connection Failed error page with Advanced panel (no option to bypass error)
Learn more link goes to https://support.mozilla.org/1/firefox/149.0/WINNT/en-US/connection-not-secure 
"Secure connection and security warning error pages in Firefox" KB article

Note: https://tls-v1-1.badssl.com:1011/  is the only test page I could find with a "Secure Connection Failed" error. 

The https://1000-sans.badssl.com/  test page used in earlier versions of the [Secure connection and security warning error pages in Firefox](https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect) KB article (see [revision 272434](https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect/revision/272434) and Image: [Fx97SecureConnectionFailed](https://support.mozilla.org/en-US/gallery/image/44969)) now produces a different error page in Firefox 140esr, 148 and 149 Beta.
Test page: https://tls-v1-1.badssl.com:1011/ 
Firefox 149 Beta Secure Connection Failed error page with Advanced panel (no option to bypass error)
Learn more link goes to https://support.mozilla.org/1/firefox/149.0/WINNT/en-US/connection-not-secure 
"Secure connection and security warning error pages in Firefox" KB article

Note: https://tls-v1-1.badssl.com:1011/  is the only test page I could find that still produces a "Secure Connection Failed" error. The test page https://1000-sans.badssl.com/ that was used in earlier versions of the [Secure connection and security warning error pages in Firefox](https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect) article (see [revision 272434](https://support.mozilla.org/en-US/kb/secure-connection-failed-firefox-did-not-connect/revision/272434) and Image: [Fx97SecureConnectionFailed](https://support.mozilla.org/en-US/gallery/image/44969)) now produces a different (time-related) error page.

Back to Bug 2021712 Comment 1