NS_ERROR_NET_RESET errors should get a more helpful error page

NEW
Unassigned

Status

()

P3
normal
3 years ago
3 years ago

People

(Reporter: past, Unassigned)

Tracking

Trunk
Points:
---

Firefox Tracking Flags

(firefox48 affected)

Details

(Whiteboard: [fxprivacy])

Attachments

(1 attachment)

Created attachment 8743897 [details]
Screenshot

In the attached error case, there are a few confusing messages to the user:

(a) the main title is "secure connection failed", but the NS_ERROR_NET_RESET error isn't related to the security aspects of the connection, muddling the waters unnecessarily
(b) the first bullet point is inaccurate, as the problem is at a lower level than authentication of received data: the connection was reset
(c) the advanced section containing the NS_ERROR_NET_RESET code may be useful to experienced users, or for reporting the error to them
(d) some report that the green padlock gives a false sense of success that is in stark contrast with the error message. Not sure that this is accurate though, the padlock is mainly indicating the security (or lack thereof) of the connection and a terminated connection is neither secure nor insecure.

Updated

3 years ago
See Also: → bug 1252068
I think the right thing to do here (a, b, c) is just to remove the distinction between a "secure connection failed" and other "connection failed" errors -- getting a FIN/RST after you send the ClientHello isn't really that different from getting one before.

With regard to (d), I agree that we should remove the padlock, and just show the (i).

Comment 2

3 years ago
(In reply to Richard Barnes [:rbarnes] from comment #1)
> I think the right thing to do here (a, b, c) is just to remove the
> distinction between a "secure connection failed" and other "connection
> failed" errors -- getting a FIN/RST after you send the ClientHello isn't
> really that different from getting one before.
> 
> With regard to (d), I agree that we should remove the padlock, and just show
> the (i).

+1
Whiteboard: [fxprivacy][triage]

Updated

3 years ago
Priority: -- → P3
Whiteboard: [fxprivacy][triage] → [fxprivacy]
You need to log in before you can comment on or make changes to this bug.