Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#12422 closed enhancement (fixed)

WebPositive enhancement for error message

Reported by: ronald-scheckelhoff-trac Owned by: pulkomandy
Priority: normal Milestone: Unscheduled
Component: Applications/WebPositive Version: R1/Development
Keywords: Error message enhancement SSL TLS failure Cc:
Blocked By: Blocking:
Has a Patch: no Platform: All

Description

When Web+ sees a page it cannot connect to because the TLS version is unaccepted or the cipher is unaccepted, it does nothing, as shown in the first image.

When Netsurf sees the same page, it displays a message, as shown in the second image.

The third image contains the Netsurf debug session for this info.

While I don't think it's necessary for a message box to appear as it does with Netsurf, it might be more user friendly for Web+ to put something on the status bar when it happens.

Attachments (5)

webpositive-tls-version-unaccepted.png (94.1 KB ) - added by ronald-scheckelhoff-trac 4 years ago.
Webpositive response to unaccepted TLS session
netsurf-unable-to-fetch-doc.png (57.8 KB ) - added by ronald-scheckelhoff-trac 4 years ago.
Netsurf response to unaccepted TLS session
netsurf-tls-version-unaccepted.png (137.4 KB ) - added by ronald-scheckelhoff-trac 4 years ago.
Netsurf debug session for this info (with same TLS situation as Web+)
WebPositive-556-debug-15-10-2015-12-24-15Y.report (23.8 KB ) - added by ronald-scheckelhoff-trac 4 years ago.
Webpositive debug report as file
NetSurf-805-debug-15-10-2015-12-25-28Y.report (31.0 KB ) - added by ronald-scheckelhoff-trac 4 years ago.
Netsurf debug report as file

Download all attachments as: .zip

Change History (10)

by ronald-scheckelhoff-trac, 4 years ago

Webpositive response to unaccepted TLS session

by ronald-scheckelhoff-trac, 4 years ago

Netsurf response to unaccepted TLS session

by ronald-scheckelhoff-trac, 4 years ago

Netsurf debug session for this info (with same TLS situation as Web+)

comment:1 by ronald-scheckelhoff-trac, 4 years ago

Note that Web+ doesn't hang or anything like that. But the status bar doesn't change, the little progress bar stays at the first tick, and it doesn't connect. But the browser is fine otherwise, and will connect to the other urls on the page.

Last edited 4 years ago by ronald-scheckelhoff-trac (previous) (diff)

comment:2 by pulkomandy, 4 years ago

Hi,

  • You can use "save report" from Debugger menu instead of attaching a screenshot. The file will be smaller and have more information.
  • A link to the website would be helpful, so I don't have to extract it from the screenshots. Is it https://forums.freebsd.org ?

by ronald-scheckelhoff-trac, 4 years ago

Webpositive debug report as file

by ronald-scheckelhoff-trac, 4 years ago

Netsurf debug report as file

comment:3 by ronald-scheckelhoff-trac, 4 years ago

Yes the url I used is https://forums.freebsd.org I've attached the debug reports (for both NS and Web+) as files. Since the Netsurf app from Haiku Depot already has debug info, and because it's real easy to download its source, I've been using NS for debugging, and just working Web+ in parallel from that - figuring the same errors on occasion - lazy, I guess. Anyway - I hope the debug output can be helpful.

Since there isn't actually any real 'broken' error, the debug report doesn't jump out at me with anything (for Web+) because it goes well past the issue. But, in the last screenshot image of the debugger, the Netsurf C source points to the issue pretty well, because I set a breakpoint. I guess I could set a breakpoint in Web+ as well ... I'm not nearly as familiar with the source of Web+, so would have to dink around. I looked at the webkit, web+, and libssl images in the Web+ debugger session searching for a bp hint. Wow, LOL. The Webkit/Web+ space is big.

@pulkomandy: This is kind of a low level "enhancement" ticket anyway. Maybe ticket 12420 is much more important. I had that one pop up again today. I forget to select the Web+ component, so you may not know about it.

Last edited 4 years ago by ronald-scheckelhoff-trac (previous) (diff)

comment:4 by pulkomandy, 4 years ago

Resolution: fixed
Status: newclosed

comment:5 by ronald-scheckelhoff-trac, 4 years ago

Just noticed this has been fixed (tested using hrev 49913) Thanks!

Note: See TracTickets for help on using tickets.