You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 5, 2019. It is now read-only.
In a nowin app, with or without nancyfx (we use nancy for development, with and without razor)
using the certificate for https, the app hangs at first or max second successfull connection, because cannot close connections to the certificate handshake, tcp ports on server side remain in "close wait" state, any new connection add another connection in this state without showing anyting,
in our case this reproducible always in a linux 64 bit machine with mono 3.x > 4.3.x (git)
with sources compiled in mono (framework 4.0) or in windows (4.2, 4.2.x) and running the compiled software in mono or official .net framwerk of both platforms, in debug mode in visual studio, the problem it's less frequently.
Looking other Bugs, seems quite similar to the "F5" bug (#52). #52
sees a memory problem, or a certificate stream problem on the passthrough after the certicate loading and become a deadlock on tcp port communication after initial connection.
service LIsten correctly but handshake remain locked on the server side.
In a nowin app, with or without nancyfx (we use nancy for development, with and without razor)
using the certificate for https, the app hangs at first or max second successfull connection, because cannot close connections to the certificate handshake, tcp ports on server side remain in "close wait" state, any new connection add another connection in this state without showing anyting,
in our case this reproducible always in a linux 64 bit machine with mono 3.x > 4.3.x (git)
with sources compiled in mono (framework 4.0) or in windows (4.2, 4.2.x) and running the compiled software in mono or official .net framwerk of both platforms, in debug mode in visual studio, the problem it's less frequently.
Looking other Bugs, seems quite similar to the "F5" bug (#52).
#52
sees a memory problem, or a certificate stream problem on the passthrough after the certicate loading and become a deadlock on tcp port communication after initial connection.
service LIsten correctly but handshake remain locked on the server side.