Closed
Bug 613175
Opened 14 years ago
Closed 11 years ago
"Secure Connection Failed" error refers to removed Help -> Report broken site command
Categories
(Core Graveyard :: Security: UI, defect)
Core Graveyard
Security: UI
Tracking
(blocking2.0 -)
RESOLVED
DUPLICATE
of bug 1014282
Tracking | Status | |
---|---|---|
blocking2.0 | --- | - |
People
(Reporter: unghost, Unassigned)
References
()
Details
(Whiteboard: [strings])
"Secure Connection Failed" error shows following text:
The page you are trying to view can not be shown because the authenticity of the received data could not be verified.
Please contact the web site owners to inform them of this problem. Alternatively, use the command found in the help menu to report this broken site.
I think that "Alternatively, use the command found in the help menu to report this broken site" part should be removed. I guess this should block Firefox 4.0b8 because it involves l10n strings.
Reporter | ||
Updated•14 years ago
|
Reporter | ||
Updated•14 years ago
|
blocking2.0: --- → ?
Comment 1•14 years ago
|
||
Do you have an example page where this string shows up?
I've tested https://master.support.mozilla.com/de/, and that actually shows about:certerror instead of about:neterror.
Whiteboard: [strings]
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1)
> Do you have an example page where this string shows up?
>
Here is example: https://www.citylink.com.au/
Comment 3•14 years ago
|
||
Right. It doesn't help that we have "Report Web Forgery…" in the Help menu, http://mxr.mozilla.org/mozilla-central/source/browser/locales/en-US/chrome/browser/safebrowsing/report-phishing.dtd#1.
That sounds like a real source of confusion. Johnath?
Comment 4•14 years ago
|
||
I agree.
Personally, I'd be happy to just see us use nssBadCert.longDesc2 ( http://mxr.mozilla.org/mozilla-central/source/browser/locales/en-US/chrome/overrides/netError.dtd#139 ) for all of these "miscellaneous nss errors".
Comment 5•14 years ago
|
||
Very few websites will cause this error to be seen. After bug 587407 is fixed this error will practically never be seen. Almost nobody will see this message after is fixed. Marking softblocker since bug 587407 was already marked softblocker.
Whiteboard: [strings] → [strings][softblocker]
Comment 6•14 years ago
|
||
Sounds like we are past the string freeze. Is it realistic that this will get done? If not, can we just minus it?
Updated•14 years ago
|
Whiteboard: [strings][softblocker] → [strings]
Comment 7•14 years ago
|
||
Yeah, not worth taking the late string hit as per comment 5.
blocking2.0: ? → -
Reporter | ||
Comment 8•11 years ago
|
||
Looks like it's been fixed in Bug 1014282
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•8 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•