Show TLS error code on the "Secure Connection Failed" error page
Categories
(Core :: Networking, enhancement, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox152 | --- | fixed |
People
(Reporter: leggert, Assigned: leggert)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(1 external file)
When a TLS handshake fails with an SSL error that isn't individually registered in the error registry (e.g. SSL_ERROR_DECRYPT_ERROR_ALERT), the nssFailure2 error page shows only generic text with no indication of what specifically went wrong. This makes it hard to diagnose what error triggered the page.
Suggested by :djackson in https://bugzilla.mozilla.org/show_bug.cgi?id=2033073#c17
| Assignee | ||
Updated•6 months ago
|
| Assignee | ||
Comment 1•6 months ago
|
||
Unregistered SSL errors that fall through to the nssFailure2 config in the
error registry now show their error code (e.g. SSL_ERROR_DECRYPT_ERROR_ALERT)
on the "Secure Connection Failed" error page, consistent with how registered
errors like SSL_ERROR_NO_CYPHER_OVERLAP already behave. Also removes a broken
third descriptionParts entry in the nssFailure2 config that referenced a
Fluent string that was never defined.
Updated•6 months ago
|
| Assignee | ||
Comment 2•6 months ago
|
||
:manuel, is there anything in this PR that should change?
Comment 4•5 months ago
|
||
Sorry, didn't have time to look at the patch. Clearing needinfo. I think showing the exact error code is good. Bug 2027209 did the same (roughly at the same time) for some other networking errors. Thanks for working on it and landing :)
Comment 5•5 months ago
|
||
| bugherder | ||
Updated•5 months ago
|
Description
•