Chris, I have done some tests and Ned is right, SSL is just broken, under heavy load after some time it gets hung and stops responding, when the remote side closes the faulted connection it starts working again.
It only happens with SSL, so it must be some bug on the SSL code on multithreading, also, when working it's slow as hell, when the conection is first made (not reused by keep-alive) it took at least 2-3 seconds to complete. For now I'm using Nginx as reverse proxy to do the https decode and it works like a charm. I will investigate further (if I can debug the mono classes) to try solve it, I have created a fork at https://github.com/gusmanb/mono and will try to keep it up to date and every finding I do will be pushed there, any contribution is wellcome. It has for now the client certificate request disabled, at least if you don't have a high load it works. It's a shame that something so basic as SSL connections don't work as expected. -- View this message in context: http://mono.1490590.n4.nabble.com/HttpListener-SSL-client-certificate-tp4663483p4663508.html Sent from the Mono - General mailing list archive at Nabble.com. _______________________________________________ Mono-list maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-list
