[Tntnet-general] tntnet-3.0 still won't accept Chrome browsers!

[Karim 'K. M. S. <hh....@go...>]

Hello,

it took us ages to upgrade to tntnet-3.0; we were using an older openssl
library with didn't work anymore with the new tntnet, and that upgrade
necessitated upgrades of half a dozen other libs in our application
which depend upon openssl. Furthermore, we had to build the static
tntnet libs by hand, as the build script just ignored any options to
that effect.

*But all those efforts were for nothing* - because updating to
tntnet-3.0 did nothing to improve our problems connecting to the web
service via Chrome-based browsers. It sill works only every 10th to 20th
time; furthermore accessing the tntnet service via Chrome now actually
crashes the application (segmentation fault in the tntnet thread) every
time we actually get passed the browser error message, whereas Firefox
still works 100% of the time and never crashes anything.

The only thing has has changed in regard to the connection errors is
that Chrome, Vivaldi, Chromium-Edge etc. now report ERR_CONNECTION_RESET
instead of ERR_CONNECTION_CLOSED.

Can anybody tell us what is the problem with tntnet and Chrome? And can
that error also lead to the segmentation faults? Is there a switch or a
debug option we can try to get closer to the source of the problem? Or
is it just hopeless to get this to work? Before we would dump even more
time into this mess, we would like to know.

Best regards
Kasi

Am 25.06.2020 um 14:34 schrieb Kasi Mir:
> Hi everyone,
> I hope anyone reads this (according to sourceforge, the last e-mail to
> this list with a reply was more than three years ago), but here we go:
>
> We're using tntnet (currently version 2.3rc1) as a web server
> engine inside our application, but have recently found out that
> chromium-based browsers (most notably Chrome itself, but also Vivaldi,
> for example) have a problem establishing a connection to our web
> service. More than nine out of ten times, we're getting back an
> ERR_CONNECTION_CLOSED in the browser, other browsers like Firefox, or
> the old Microsoft Edge display the page 100% of the time. The
> connection in question is encrypted, the web service in our project
> only allows for encrypted connections, so I don't really know whether
> the encryption plays a part in this. 
>
> Using the Chrome DevTool (network tab), I see that when it fails, the
> connection pretty much fails immediately, no additional resources from
> the page (a login screen) are loaded:
>
> image.png
>
> Every now and then, however, the connection works just fine, as with
> any other browser: 
>
> image.png
> As I've "inherited" this part of our project from a former colleague,
> I'm just getting acquainted with tntnet and a little unsure where to
> look for the source of this problem. Thus, I thought I'd ask the users
> of this mailing list (in any):
>
>  1. whether this is a known error with tntnet and chrome, perhaps one
>     fixed in a later version of tntnet, and/or
>  2. for pointers to where I should start to look for the root of the
>     problem. 
>
> Any help is appreciated. 
>
> Best regards
> Kasi
>
>
>
>
>
>
>
>
>
>
>
>
>