Opened 3 years ago

Last modified 3 years ago

#12865 new bug

Unrecognized SSL errors are only printed to stdout, not shown to the user

Reported by: waddlesplash Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Applications/WebPositive Version: R1/Development
Keywords: Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

On sites that throw unrecognized SSL errors, the messages are only printed to stdout. Sometimes the errors are fatal, and so the user has no way of knowing why the page stopped loading.

Change History (2)

comment:1 Changed 3 years ago by vidrep

The following URL provides a test case: https://my.justenergy.com/

comment:2 Changed 3 years ago by pulkomandy

That URL does not show SSL errors anymore.

BSecureSocket is handling these errors and it is properly returning B_ERROR when they happen, it is up to the application to handle that. An API to get an user readable error string in case of error would be nice, but showing SSL errors directly to the user would not be very nice anyway.

Are there pages where such errors actually happen? (not because of bugs in our implementation, I mean).

Note: See TracTickets for help on using tickets.