SSL network error should perhaps say there's an issue with the website / connection when prefs are the default
Categories
(Firefox :: Security, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox49 | --- | affected |
People
(Reporter: jkt, Unassigned)
References
Details
Updated•9 years ago
|
Updated•3 years ago
|
Comment 4•3 years ago
|
||
The severity field for this bug is relatively low, S3. However, the bug has 3 duplicates.
:serg, could you consider increasing the bug severity?
For more information, please visit auto_nag documentation.
Comment 5•3 years ago
|
||
error: "a secure connection can not be established; the authenticity of received data could not be verified; please report this to the site owner::"
It needs to give a detailed description on why the authenticity could not be verified as well as the option to ignore that like the default at http. Depending on this data the user will be capable to figure out whether the problem may likely be temporary (as in my case) or whether it is f.i. a consequence of the site owner not having updated the security certificate. An error message as general as this does not help and I believe this issue shall really be fixed.
Comment 6•3 years ago
|
||
A retry button does f.i. not help for an outdated certificate so please give the option to ignore the error. Severity shall be higher than S3. There must be a way to view the site.
Comment 7•3 years ago
|
||
The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.
Description
•