Jan Vidar Krey 35d8088b44 Handle socket errors from connected clients. ... If a TLS error occurs, it could end up in a situation where the network handler code did not want to read or write because it only had the error flag set. However, this was not handled, which left the socket triggering in the event loop - but nothing was done to handle it. This can easily cause a 100% cpu situation - the hub is still functioning though while this is happening.		2019-12-13 10:51:40 +01:00
..
adc	Secure URLs: http --> https (part 2)	2019-04-23 15:59:03 +02:00
core	Handle socket errors from connected clients.	2019-12-13 10:51:40 +01:00
network	Add statistics about OpenSSL events such as handshakes, closes and errors.	2019-06-18 15:59:22 +02:00
plugin_api	Secure URLs: http --> https (part 2)	2019-04-23 15:59:03 +02:00
plugins	Secure URLs: http --> https (part 2)	2019-04-23 15:59:03 +02:00
tools	Secure URLs: http --> https (part 2)	2019-04-23 15:59:03 +02:00
util	Secure URLs: http --> https (part 2)	2019-04-23 15:59:03 +02:00
system.h.in	Secure URLs: http --> https (part 2)	2019-04-23 15:59:03 +02:00
uhub.h	Secure URLs: http --> https (part 2)	2019-04-23 15:59:03 +02:00
version.h.in	Secure URLs: http --> https (part 2)	2019-04-23 15:59:03 +02:00