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: image.png] Every now and then, however, the connection works just fine, as with any other browser: [image: image.png] As I've "inherited" this part of our project from a former colleague, I'm just getting acquainted with tntnet and am 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
_______________________________________________ Tntnet-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tntnet-general
